Awesome! That is exactly what acme-http is for! I am definitely
interested in figuring out ways to improve acme-http so that it can be
a better reference for 'best practices' when it comes to high
performance HTTP servers. So, if you discover techniques that can be
applied to acme-http I am very interested in hearing about them.
Especially when it comes to the 'black magic' parts. acme-http makes
no attempts to decode the request body.. because making a faster
multipart/form-data decoder is relatively straight-forward. With
acme-http I want to explore the more mysterious bottlenecks -- things
like maxListenQueue, TCP_NODELAY, etc.
Thanks!
- jeremy
On Wed, Oct 10, 2012 at 8:11 PM, Kazu Yamamoto
Hi,
warp relies on network-conduit which uses maxListenQueue. I will fix this anyway.
acme-http specifies (max 1024 maxListenQueue) to the listen queue. I like this approach. So, I fixed network-conduit in the same way.
https://github.com/kazu-yamamoto/conduit/commit/5b1f9f05405abb11a8bc0893c0cd...
P.S.
I will fix documentation only for the network package.
--Kazu
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel