This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigBAA28A362493814AD72FBA79
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Artem Kazakov wrote:
> So I want to utilize IP-sharing and TCP-connection synchronization
> (which is not yet implemented by anyone as far as I know). I want it
> in case of failure seamlessly to switch to the other machine. As far
> as the internal state is synchronized, if it is possible to
> synchronize open connections as well(and all the low level stuff as
> packet sequence numbers and so on) it would allow to make switch-over
> to the back-up server in a matter of seconds, and the clients would
> stay connected.
I don't know if you already considered this, but the above looks like=20
both machines would simultaneously process a single TCP connection. So,=20
when a TCP connection request (handshake) arrives, you want both of the=20
machines to respond?
Further on: You'll confuse the remote application and waste bandwidth if =
you send two responses to every TCP packet you receive.
And on: What about the applications running on the two machines: if the=20
remote client send e.g. a request to delete a resource (just an=20
example): would both servers receive and respond to the request?
etc, etc.
Have you read the manual for carp(4) and why isn't CARP good enough for=20
what you need?
--------------enigBAA28A362493814AD72FBA79
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFG5+BoldnAQVacBcgRAy7XAJ4o0zli6gEEQe/EPkGzoPARhcM6yACbBLvc
iO+GYZnleStHRrfpsVWtnyw=
=2PlV
-----END PGP SIGNATURE-----
--------------enigBAA28A362493814AD72FBA79--