If your traversing from one stand alone AP to another, the client will need to make a new DHCP request on each AP it attempts to join, as stand alone AP's are not aware of each other.
The main thing here is the client has to go through Layer 2 entry on every AP, and if you have a passphrase on every AP, it wil have to go through the handshake mechanism, which adds delay and you will drop a few packets.
Once authenticated the clients will then be held in the connected/unconnected client cache of all the AP's in the network, until either the AP is rebooted, or the cache is overwritten or purged
Note: I am unsure as toward how long a stand alone AP stores the unconnected client cache
If you want fast/seemless transition between each AP, you must use a ZD as that supports 802.11r/k.
802.11r/k are not supported on stand alone AP's at the moment...
You may also want to consider the following options in the cli of your stand alone AP's to assist with roaming, as certain device hold on to AP's which can impact client performance:
set ofdm-only
set bss-minrate 24
set roam_factor wlanX <1-10>
For a full explanation towards the configuration of smart-roam see the following:
https://support.ruckuswireless.com/answers/000002277I personally have seen great results using this in large scale roaming networks, but the link above does mention that some Apple devices dont like it - it's worth a test, as I have seen no issues when using it so far.
One note is that if you use a ZD, you must configure the session idle timeout on the WLAN to marry up with your DHCP server session idle timeout, or the set it to the max value of 500mins.