Alexander Vershilov

I've added a new primitive to keep code backward compatible.

We can close this issue now, I don't easily see that #281 was merged, at least it's marked as open on github, but we can check while processing #281.

Addressed in PR #184.

I really like the general concept and ideas. There are still many questions about how to implement concrete steps. I think it make sense on selecting the really core of...

@hyperthunk I'd rather not looking at the network layer at all as at thing point of time the most interesting thing is to have nice abstractions that allow us to...

In `CCI` they use to a. use process buffers for messages in order to avoid uncontrollable memory usage by network library, also asynchronous operations returns `Handle` that client could use...

It's simply a matter of adding log output in exception handler: https://github.com/haskell-distributed/distributed-process/blob/master/src/Control/Distributed/Process/Node.hs#L254-L260 I think writing to `stderr` will be fine because there are no other mechanism exists and there is...

I agree to make such patch, but I'm not sure what will our strategy be here, and as consequence what to put into deprecation message. Will `DEPRECATED withMonitor "this function...

@hyperthunk how much effort do you plan to put into d-p now, if there will be enough changes for the major release, we can just remove the message, and write...

Ok, then we should verify that everything is in master and provide deprecation message, will you do that yourself or want me to take care of that.