And that is where the confusion begins. By kicking off the client (a deauth request), the AP is simply telling the client to disconnect from it. The client may decide to reconnect to the same AP or try another AP, based on it’s association algorithms.
Careful using the term load-balancing. Most enterprise-grade vendors which have AP load balancing or band-balancing do their ‘balancing’ at the moment of association. Once a client is associated, LB/BB never kicks out forcefully as that will trigger an emergency/reactive roam.
Of course, since it’s a client-driven process and there are no standards defined on the roaming algorithms, how quickly the emergency roam takes depends entirely on the clients.
Good for you, it just means your client devices are very good roamers.
Read my post again, I specify that using a MT device as a station results in poor roaming, because MikroTik is not designed to roam quickly and therefore has practically zero roaming processes. It simply waits until the signal is too low, disconnects, looks for new APs, and joins strongest signal.
Also, Skype is designed to work in the wild west internet, so has very good adaptive algorithms and would probably work well even if used over a MT in station mode. Try doing the same with SIP or an old console-based application or a MS Access database.
If it works well for your application, go for it. The point of this discussion is different. OP asked that “CAPsManager should support Roaming between networks” and a lot of misinformation ensued (including yours I’m afraid), so I wanted to set the record straight on how 802.11 WiFi works.