You could just use Unix sockets. You ca n create those with the standard network library if I recall correctly.
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 <cma@bitemyapp.com> wrote: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/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:_______________________________________________CorentinThanks!It is used in Hint-server: http://hackage.haskell.org/package/hint-serverby something more mainstream.Essentially, I would to replace this library http://hackage.haskell.org/package/eprocessHello,what would you recommend as a message passing library?
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
--Chris AllenCurrently working on http://haskellbook.com
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe