Excellent! Glad this has been sorted out upstream.<div><br></div><div>Edward, to answer your question regarding blocking database calls: I'm using mongoDB to log events that come into a WAI webapp. The writes to mongo are blocking, so I'd like to run them in parallel with the webapp. The webapp would push the data into a Chan and the mongo writer would read from the Chan and make the writes sequentially (using the Chan as a FIFO between parallel threads). This would allow for request rates to temporarily rise above mongo's write rate (of course with an expanded memory footprint during those bursts).</div>
<div><br></div><div>Mike S Craig<br><br><br><div class="gmail_quote">On Thu, Dec 1, 2011 at 12:10 PM, Felipe Almeida Lessa <span dir="ltr"><<a href="mailto:felipe.lessa@gmail.com">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 class="im">On Thu, Dec 1, 2011 at 2:40 PM, Edward Z. Yang <<a href="mailto:ezyang@mit.edu">ezyang@mit.edu</a>> wrote:<br>
> Simon Marlow investigated, and we got this patch out:<br>
<br>
</div>Nice work, guys! Hope it gets included in the glourious GHC 7.4 =D.<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Felipe.<br>
</font></span></blockquote></div><br></div>