Let's say we have two computers running our software. One of them is on
IP1
and the other IP2. If the IP1 fails for hardware/software reason, IP2
should
be answering as if IP1 has never failed or with some low interval.
Something
like NLB but with failover support as we will have full application-aware
layer (HTTP(S)).
In my opinion, this could be made with DNS or with DHCP IP change from IP2
to IP1 of the machine who use to have IP2.
DNS, maybe. Problem when client has fixed IP configured.
DHCP, probably not. How would the client know the new IP ?
Francois and I wonder what else methods people on the list might
suggest(?)
Using BigIP product (http://www.f5.com/products/big-ip/) or similar.
Using Windows Clustering (never used nor even studied it).
--
[email protected]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
