Hi,
the actor package seems unmaintained and probably doesn't fit your needs. If
you want to implement some kind of publish/subscribe system over the
network, I'd suggest you take a look at ZeroMQ[1] and AMQP[2].
AMQP is probably easier to get started with, but it requires you to set up a
On Mon, Aug 15, 2011 at 12:36 PM, Holger Reinhardt hreinha...@gmail.comwrote:
Hi,
the actor package seems unmaintained and probably doesn't fit your needs.
If you want to implement some kind of publish/subscribe system over the
network, I'd suggest you take a look at ZeroMQ[1] and AMQP[2].
It seems that the recent Cloud Haskell paper is relevant:
http://research.microsoft.com/en-us/um/people/simonpj/papers/parallel/remote.pdf
The repo is here:
https://github.com/jepst/CloudHaskell
I haven't tried it yet myself but would like to.
Cheers,
-Ryan
On Mon, Aug 15, 2011 at
On Mon, Aug 15, 2011 at 11:41 PM, Ryan Newton rrnew...@gmail.com wrote:
It seems that the recent Cloud Haskell paper is relevant:
http://research.microsoft.com/en-us/um/people/simonpj/papers/parallel/remote.pdf
The repo is here:
https://github.com/jepst/CloudHaskell
I haven't tried
On Sat, Aug 13, 2011 at 3:54 PM, dokondr doko...@gmail.com wrote:
Hi,
I am trying to figure out what Haskell libraries can be used to build
publish / subscribe communication between threads running both in the same
and different address spaces on the net.
For my needs any of these models
Hi,
I am trying to figure out what Haskell libraries can be used to build
publish / subscribe communication between threads running both in the same
and different address spaces on the net.
For my needs any of these models will work:
- Actors [ http://en.wikipedia.org/wiki/Actor_model ]
- Linda
