[e-lang] [Fwd: Re: Proposal: E / Erlang integration]

David Hopwood david.nospam.hopwood@REDACTED
Fri Jun 9 06:55:10 CEST 2006


I wrote:
> Hmm, maybe selective receive would be beneficial here. I don't think it is
> incompatible with the rest of E's concurrency model, and I think it can be
> implemented purely in E as a reusable abstraction (using an actors-style
> 'receptionist' that buffers messages until they can be matched -- see
> section 3.6 of <http://www.cypherpunks.to/erights/history/actors/AIM-781.pdf>).
> 
> OTOH, I'm not entirely convinced that buffering messages until we leave the
> waiting state (as the Erlang code implicitly does) is exactly the right thing.
> For example, if we get an 'offhook' message, or if the hardware fails, then the
> message buffer should be flushed. I don't think there's any way to do that in
> Erlang (there is with the receptionist approach).

Another reason to be dubious about the way Erlang handles selective receive
is the performance issue described in
<http://www.erlang.org/ml-archive/erlang-questions/200511/msg00154.html>.

-- 
David Hopwood <david.nospam.hopwood@REDACTED>





More information about the erlang-questions mailing list