Greetings, Is there a recommended/common pattern for deploying mongrel2 and enabling high availability and increasing the reliability of the service, that is, reduce the single point of failure of having one mongrel2 entry point machine?
Is it possible to have redundant mongrel2 machines, in a way that if one goes down, the other can reliably continue/respond the connections from the previous? My understanding is that a mongrel2 instance stores connection state, so I am not sure if this is possible? Should the client and backend solve this by resending on timeout and being idempotent? Ideas regarding this are welcome. att, -- Paul Eipper
