What isn't satisfactory with what you currently have? Are you just looking
for more support so you don't have to DIY? Cloud Haskell and Courier both
have an in-memory backends, so I'm not sure how to whittle things down yet
without other candidate libraries/tech to consider. The only other options
that come to mind right now as being related to message passing go in the
opposite direction of what you want, like Kafka.
On Mon, Jul 20, 2015 at 11:50 AM, Corentin Dupont wrote: Actually I only need to pass messages between processes with a queue...
No need for network... Sorry it was not clear :) On Mon, Jul 20, 2015 at 6:27 PM, Christopher Allen I believe the primary contenders would be Cloud Haskell [1] and Courier
[2]. [1]: http://hackage.haskell.org/package/distributed-process and
http://haskell-distributed.github.io/ [2]: http://hackage.haskell.org/package/courier Cloud Haskell is probably more widely used. I don't know if they're
leveraging Static Pointers yet, but the feature was motivated in part by
their needs. We mostly use Pipes, TCP sockets, and Binary but I think you're looking
for something more reliable. Probably someone will recommend ZeroMQ. I'd
steer clear of ZeroMQ unless you have an intimate understanding of it and
how to work around its quirks. On Mon, Jul 20, 2015 at 11:22 AM, Corentin Dupont <
corentin.dupont@gmail.com> wrote: Hello,
what would you recommend as a message passing library?
Essentially, I would to replace this library
http://hackage.haskell.org/package/eprocess
by something more mainstream.
It is used in Hint-server:
http://hackage.haskell.org/package/hint-server Thanks!
Corentin _______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe --
Chris Allen
Currently working on http://haskellbook.com --
Chris Allen
Currently working on http://haskellbook.com