why concurrency in the first place?
Wed Feb 7 21:11:24 CET 2001
I find this discussion very interesting.
But right now I'd like to ask something about something Ulf said:
From: "Ulf Wiger" <>
> Looking into, say, the A side half-call, you will find several
> independent state machines. They are not concurrent in one sense, as
> their state transitions are tightly coupled, but you can, for example
> replace one (protocol) layer 3 FSM with another. As it turns out,
> implementing these FSMs as separate processes in Erlang would be a
Why would it be a mistake? (I can think of some reasons, but I'd like to hear yours... :-)
Is it the tight coupling? Efficiency? A design 'no-no'?
More information about the erlang-questions