<br><br><div class="gmail_quote">On Wed, Aug 3, 2011 at 1:50 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<div><div></div><div class="h5"><br>
On Wed, Aug 03, 2011 at 01:42:13AM +0800, David Yu wrote:<br>
<br>
> On Wed, Aug 3, 2011 at 1:36 AM, Maxim Dounin <<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>> wrote:<br>
><br>
> > Hello!<br>
> ><br>
> > On Tue, Aug 02, 2011 at 04:24:45PM +0100, António P. P. Almeida wrote:<br>
> ><br>
> > > On 1 Ago 2011 17h07 WEST, <a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a> wrote:<br>
> > ><br>
> > > > Hello!<br>
> > > ><br>
> > > > JFYI:<br>
> > > ><br>
> > > > Last week I posted patch to nginx-devel@ which adds keepalive<br>
> > > > support to various backends (as with upstream keepalive module),<br>
> > > > including fastcgi and http backends (this in turn means nginx now<br>
> > > > able to talk HTTP/1.1 to backends, in particular it now<br>
> > > > understands chunked responses). Patch applies to 1.0.5 and 1.1.0.<br>
> > > ><br>
> > > > Testing is appreciated.<br>
> > > ><br>
> > > > You may find patch and description here:<br>
> > > ><br>
> > > > <a href="http://mailman.nginx.org/pipermail/nginx-devel/2011-July/001057.html" target="_blank">http://mailman.nginx.org/pipermail/nginx-devel/2011-July/001057.html</a><br>
> > > ><br>
> > > > Patch itself may be downloaded here:<br>
> > > ><br>
> > > > <a href="http://nginx.org/patches/patch-nginx-keepalive-full.txt" target="_blank">http://nginx.org/patches/patch-nginx-keepalive-full.txt</a><br>
> > > ><br>
> > > > Upstream keepalive module may be downloaded here:<br>
> > > ><br>
> > > > <a href="http://mdounin.ru/hg/ngx_http_upstream_keepalive/" target="_blank">http://mdounin.ru/hg/ngx_http_upstream_keepalive/</a><br>
> > > > <a href="http://mdounin.ru/files/ngx_http_upstream_keepalive-0.4.tar.gz" target="_blank">http://mdounin.ru/files/ngx_http_upstream_keepalive-0.4.tar.gz</a><br>
> > > ><br>
> > ><br>
> > > So *either* we use the patch or use the module. Correct?<br>
> ><br>
> > No, to keep backend connections alive you need module *and* patch.<br>
> > Patch provides foundation in nginx core for module to work with<br>
> > fastcgi and http.<br>
> ><br>
> With a custom nginx upstream binary protocol, I believe multiplexing will<br>
> now be possible?<br>
<br>
</div></div>ENOPARSE, sorry.<br></blockquote><div>After some googling ... </div><meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 13px; ">ENOPARSE is a nerdy term. It is one of the standard C library error codes that can be set in the global variable "errno" and stands for Error No Parse.<br>
</span><div><span class="Apple-style-span" style="font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; font-size: 13px; ">Since you didn't get it, I can thus conclude that unlike me you are probably a normal, well adjusted human being ;-)</span> </div>
<div><br></div><div>Now I get it. Well adjusted I am.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br>
Maxim Dounin<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>When the cat is away, the mouse is alone.<br>- David Yu<br>