
On Wed, Aug 22, 2012 at 8:30 AM, Felipe Almeida Lessa < felipe.lessa@gmail.com> wrote:
On Tue, Aug 21, 2012 at 9:01 PM, Thiago Negri
wrote: My view of Cloud Haskell usage would be something similar to this: a master node sending work to slaves; slave instances getting up or down based on demand. So, the master node should be slave-failure-proof and also find new slaves somehow.
Am I misunderstanding the big picture of Cloud Haskell or doing anything wrong in the following code?
(Disclaimer: I can't speak for Cloud Haskell's developers.)
AFAIK this is CH's goal. However, they're not quite there yet. Their network implementation is still a lot naive as you're seeing =).
I believe this behavior is due to the usage of channel, you just need to implement some kind of timeout function.
Cheers,
-- Felipe.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe