[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Anyone up for porting Termite to Chicken?

From: Alaric Snell-Pym
Subject: Re: [Chicken-users] Anyone up for porting Termite to Chicken?
Date: Tue, 20 May 2008 19:17:10 +0100

On 20 May 2008, at 3:16 pm, Alaric Snell-Pym wrote:

IIRC there's more to it than that. As well as passing messages back
and forth, Erlang also has mechanisms for passing uncaught exceptions
in the top-levels of processes back to processes waiting for messages
from that process... or something like that. Something that prevents
deadlock situations where a client thread is waiting for a response
from a server thread that dies, without extra programmer effort,

I now can't find any reference to this thing - I may be mistaken :-)
The closest I've come is:

So it looks like the 'fun features' of Erlang's concurrency system
compared to what I know of MPI are:

1) Dynamic spawn-arbitrary-process-on-arbitary-node distributed
2) Hot code loading:
3) Ease of building monitoring systems by being able to register to
receive termination notices of processes

However, MPI has loads of tools for distributed numerical algorithms!
Lots of group communication stuff, the cartesian topology stuff I
don't really understand, etc.

I think Erlang's model is more aimed towards highly dynamic client/
server transaction processing stuff (like most Internet
applications), while MPI is hot for doing giant matrix operations and
predicting the weather.


Alaric Snell-Pym

reply via email to

[Prev in Thread] Current Thread [Next in Thread]