FSM advantages?

[martin j logan]

Module:StateName(Event, StateData) -> Result

      Types:
            Event = timeout | term()

-Martin


On Thu, 2003-01-23 at 08:18, Inswitch Solutions - Erlang Evaluation
wrote:
> Martin,
> 
> Thank you I've found the  function
> sync_send_event(FsmRef, Event, Timeout) -> Reply
> which does exactly what I need.
> 
> I just only need to know what's the reply term when the Timeout ocurr?
> 
> 
> Regards,
> Eduardo Figoli
> INSwitch Solutions
> 
> 
> ----- Original Message -----
> From: "martin j logan" <martin@REDACTED>
> To: "Inswitch Solutions - Erlang Evaluation" <erlang@REDACTED>
> Cc: <erlang-questions@REDACTED>
> Sent: Wednesday, January 22, 2003 7:11 PM
> Subject: Re: FSM advantages?
> 
> 
> The fsm is fine for an automaton with time constraints. gen_fsm supports
> user defined states and user defined transitions between those states.
> Any state can be augmented with a timeout. A programmer can specify the
> behavior of the fsm when such a timeout occurs.
> 
> Cheers,
> Martin
> 
> 
> On Thu, 2003-01-23 at 02:31, Inswitch Solutions - Erlang Evaluation
> wrote:
> > Hi !
> >
> > Thank you for your answers.
> > Suppose I have to implement a timed automata (timed temporal graph) in
> > Erlang.
> > Would FSM be the right choice to receive/send messaging with "after"
> > timeouts ?
> > A finite state machine (FSM) says what to do and a timed automata is a
> > finite state machine but also saying when (time) to do it.
> > Does someone already get in touch with implementations in Erlang for
> > this type of Real Time systems model ?
> >
> >
> > Regards,
> > Eduardo Figoli
> > INSwitch Solutions
> >
> >
> > ----- Original Message -----
> > From: "Vlad Dumitrescu" <vlad_dumitrescu@REDACTED>
> > To: <erlang-questions@REDACTED>
> > Sent: Tuesday, January 21, 2003 9:00 AM
> > Subject: Rw: FSM advantages?
> >
> >
> > Hi,
> >
> > Adding to Vance's comment, let's not forget that the predefined behaviours
> > do quite a lot of things behind the scenes, things that otherwise need to
> be
> > handled explicitly. Among them: tracing and error reporting, code change,
> > works in a supervision tree, a standardized API.
> >
> > For a simple FSM, it is quite educative to implement it as a basic
> > function-based one. The next step would be trying to introduce one of the
> > things mentioned above, and I think it will be easy to appreciate that one
> > could use the already written and tested ones instead.
> >
> > best regards,
> > Vlad
> > -----Original Message-----
> > From: Inswitch Solutions - Erlang Evaluation [mailto:erlang@REDACTED]
> > Sent: Tuesday, January 21, 2003 1:58 PM
> > To: erlang-questions@REDACTED
> > Subject: FSM advantages ?
> >
> >
> >
> > Could someone tell me the advantages of using
> > FSM to Erlang receive & send messaging using functions (states), please ?
> >
> >
> > Thanks,
> > Eduardo Figoli
> > INSwitch Solutions
> >
> >
> >
> >
> >
> >
> >
> >
> > _________________________________________________________________
> > Senaste nytt från motormarknaden http://motor.msn.se/
> >
> >
> 
> 
>