If you use different channels, and don't use WDS, doesn't this mean the client has to drop association with the first radio card before it can associate with another? If so, the resulting experience for the user is temporary loss of connectivity (and probably dropped VoIP/streaming media) at each transition.
It's my understanding that weather or not it's on the same channel doesn't matter, the behavior would be the same. It would disassociate from one, then associate to the other.
Regardless, why would you intentionally gimp your system? If you run all three sectors on the same channel, you'll have huge CSMA and CCQ issues, and major problems with collisions.
Which begs the question: is there another way to get radios to hand clients to each other seamlessly, without putting them on the same channel and using WDS?
To my understanding 802.11 does not support seamless roaming.
From
Cisco Press:
The Nature of Roaming in 802.11
802.11 roaming is known as "break before make," referring to the requirement that a station serves its association with one AP before creating an association with a new one. This process might seem unintuitive because it introduces the possibility for data loss during roaming, but it facilitates a simpler MAC protocol and radio.
If 802.11 were "make before break," meaning a station could associate to a new AP before disassociating from the old AP, you would need safeguards in the MAC to ensure a loop-free topology. A station connected to the same Layer 2 broadcast domain via simultaneous network connections has the potential to trigger broadcast storms. A "make before break" architecture would necessitate an algorithm such as 802.1D spanning tree to resolve any potential loops, adding overhead to the MAC protocol. In addition, the client radio would have to be capable of listening and communicating on more than one channel at a time, increasing the complexity of the radio (and adding to the overall cost of the devices).