add OTP style framework of standard *behaviours* about distributed-process HOT 10 CLOSED

Yes, various people have talked about this. It's outside the scope of the Cloud Haskell project proper, so I would suggest you start a separate Github repository for it and invite people on Twitter to contribute to it (I'll be happy to retweet, a number of people have asked about OTP on twitter). I suggest 'distributed-process-platform' for the name of the package.

from distributed-process.

I'm happy enough to answer questions (by email, or on the parallel-haskell mailing list) but cannot contribute myself.

from distributed-process.

Ok great - I'll start a new repo and come ask questions on the mailing list (which I didn't know existed!) as and when I need to. Thanks!

from distributed-process.

This site page for documenting interest right?

from distributed-process.

For now.

from distributed-process.

<- interest

from distributed-process.

Likewise, interested. OTP isn't so much a requirement as a natural evolution of having distributed processes and process trees and wanting to manage them sanely.

from distributed-process.

FWIW as a professional erlang programmer, I suspect many of the otp concepts are I'll fitting to cloud Haskell. For example, gen_server is probably far less useful than a set o abstraction for working with typed or untyped channels in a consistent way (request/reply channels, higher order/delegated channels and the like). The supervisor concept is definitely worth porting however, and the application concept maybe have a place too.

I will post back when I get around to setting up a repo an for those who live in/around London, I'll be attending the next LHUG meeting later this month.

from distributed-process.

Guys - please add ideas/feature requests to the issue tracker at hyperthunk/distributed-process-platform. I am not as hot a Haskell hacker as I am an Erlang/ML one, so of course suggestions and contributions will be most welcome. In particular I'm keen to get early feedback on the model for describing type constraints within the various generic moving parts, staring with supervision trees. And feel free to spread the word on the mailing list do we can have a wider discussion. I'll post something tonight to kick that off.

from distributed-process.

Great, thanks!

from distributed-process.