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