tonyshowoff
|
Yes, but only with clients, IIRC around 2.0 and higher. Essentially when a server either needed to go down the client was sent a service relocation notice with provided IP, and then in the background it simply signs on to the new provided server. When this happens the user state remains in the system so someone may not look like they've changed servers or reconnected, even when they have.
This didn't always work seamlessly though, sometimes the client may not notice but all his buddies would see a new sign on time, or all his buddies would sign off and then sign back on, for example if he got moved to a new feedbag (buddy server) that was slow to update the state or something.
There are various reasons for these, but overall the main idea was more to make sure the user *experienced* uninterrupted service rather than worrying about sign on times, which typically was never allowed to be more than 15 days due to various technical reasons though it's possible to go over that.
|