10-04-2017, 07:46 PM
Dynamic TCP Connection Elapsing
When designing systems for process migration,load-balancing, or fail-over,
there comes point where one would like to move a socket from one
machine to another machine, without losing the connection on that socket,
similar to file descriptor passing on a single host.
Such a move operation usually involves three elements:
1)Making sure that packets belonging to the connection are sent to the
new owner of the socket.Automatically, this also means that the previous
owner should no longer receive the data packets.
2)Moving any application space state related to the connection to the
new owner.For example,taking the case of a Web server storing large
static files, the application state can be the file name and the
current position in the file.
3)The last and the important one: creating compatible network state
in the kernel of the new connection such that it can resume the
communication where the previous owner left off.
The origin server transfers the application state to the destination
server where the application state resides in the user space. Also
the kernel state is transferred from the origin server to the
destination server and the necessary packet routing being provided
by the peer(client).
Further details can be found in this link:
http://smartlogixtechnicalarticles/dynam...-elapsing/