On Friday, 30 March 2012 00:53:48 UTC+4, Jeremy Shaw  wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div>We are pleased to announce the &nbsp;release of Happstack 7!</div><div><br></div><div>Happstack is a fast, modern, web application framework written in Haskell. Please check out the brand new <a href="http://happstack.com" target="_blank">happstack.com</a> website to read about what is new in Happstack 7, and what we are planning for Happstack 8, and what makes Happstack great!</div>
<div><br></div><div><a href="http://www.happstack.com/" target="_blank">http://www.happstack.com/</a></div><div><br></div><div>- jeremy</div></blockquote><div><br></div><div>Congratulations to the new release, and may I say that the homepage looks smashing! :D</div><div><br></div><div>With the work of Antoine Latter's happstack-wai (https://github.com/aslatter/happstack-wai), it's likely possible to serve happstack applications through my (still in development) SPDY WAI server (<a href="https://github.com/kolmodin/spdy">https://github.com/kolmodin/spdy</a>) although I have not tested this combination yet.</div><div><br></div><div>Before I saw happstack-wai I had a quick look at the happstack API and saw that the Request keeps the request body as a (lazy?) String. I'm curious to the rationale for this, as one could expect a lazy bytestring would be more efficient, and some kind of stream would better support error handling (given that the String is indeed lazy). Sorry if this has been discussed before, I searched the mailing list without finding anything.</div><div><br></div><div>Feels like Happstack has been reborn, thanks again!</div><div><br></div><div>Cheers,</div><div>&nbsp; Lennart</div>