[erlang-questions] Newbie question, finite state Machine failover

[Jon Watte]

Stateful, as in the fail-over needs to be "hot" and "online" and replicating
the state of the first application faithfully?

The danger with such approaches is that, if the state becomes corrupt
through some chain of events, then the replicated copy may also be corrupt,
and the "slave" crashes when the "master" crashes. It still works great in
case of hardware failure on the master instance, of course.

Sincerely,

jw


--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.



On Sun, Sep 4, 2011 at 9:06 AM, Thomas Elsgaard
<thomas.elsgaard@REDACTED>wrote:

> Hi
>
> I am looking into using erlang for a FSM (finite state machine) and i will
> need to implement a statefull failover mechanism between two physical
> servers, which approch would you recommend for this? Any Best practice
> advices?
>
> Thomas
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110906/ff9d3865/attachment.htm>