distributed-process
distributed-process copied to clipboard
haskell-distributed
Cloud Haskell core library
I see no reason why we should copy data that's being passed between two processes on the same (local) node. So I've started experimenting with skipping some of the overhead...
Erlang uses cookies to authenticate nodes; we could do something similar or something much more sophisticated. This should be done in individual backends, as security might vary widely from one...
Messages sent by Cloud Haskell processes are always sent whole, independent of their size. This means that when a process sends a very large message, it can hog the network...
Small CH messages have a large overhead. For instance, consider sending `(Nothing :: Maybe ProcessId)`. The binary encoding of `Nothing` is one byte, but the total message sent looks like...
(I'm sorry for this being not exactly Haskell) I wan to run C.H. on a cluster where the main node has several network interfaces: ``` Destination Gateway Genmask Flags Metric...
It would be nice if the haskell-distributed organisation had a sexy looking web site that links off to CH and -platform and so on. If we use Jekyll and github...
Perhaps this is too much to hope for, but it would be ideal for packages such as meta-par, HDpH and distributed-process to be able to share basic RPC functionality (Closure/Static)....
Write a script-driven `Network.Transport` implementation with which we can test for specific network failures, and then use QuickCheck to generate scripts (similar to how `ByteString` is tested).
In line with issue #97 there are times when you'd like to get an overview of running processes in your system. Issue #89 is already starting to provide some of...