Open Server supports seamless migration of the client’s connection. However, the responsibility of sharing and migrating the client’s context lies with your application. You can implement context migration in different ways, such as through a shared file system or a network communication.
For an in-batch migration, the server that the client is migrating to does not know what type of event was raised in the original server. If your application needs this information, you must migrate the information as part of the client’s context.
With idle migration, the client is not waiting for actual results from Open Server. Because there is no active query to migrate, idle migration is easier to implement than in-batch migration. However, idle migration still requires that your application fulfills any pending requests that may arrive before the client starts the migration.
