Hello!
On Wed, Aug 03, 2011 at 01:42:13AM +0800, David Yu wrote:
> On Wed, Aug 3, 2011 at 1:36 AM, Maxim Dounin <mdounin@mdounin.ru> wrote:
>
> > Hello!
> >
> > On Tue, Aug 02, 2011 at 04:24:45PM +0100, António P. P. Almeida wrote:
> >
> > > On 1 Ago 2011 17h07 WEST, mdounin@mdounin.ru wrote:
> > >
> > > > Hello!
> > > >
> > > > JFYI:
> > > >
> > > > Last week I posted patch to nginx-devel@ which adds keepalive
> > > > support to various backends (as with upstream keepalive module),
> > > > including fastcgi and http backends (this in turn means nginx now
> > > > able to talk HTTP/1.1 to backends, in particular it now
> > > > understands chunked responses). Patch applies to 1.0.5 and 1.1.0.
> > > >
> > > > Testing is appreciated.
> > > >
> > > > You may find patch and description here:
> > > >
> > > > http://mailman.nginx.org/pipermail/nginx-devel/2011-July/001057.html
> > > >
> > > > Patch itself may be downloaded here:
> > > >
> > > > http://nginx.org/patches/patch-nginx-keepalive-full.txt
> > > >
> > > > Upstream keepalive module may be downloaded here:
> > > >
> > > > http://mdounin.ru/hg/ngx_http_upstream_keepalive/
> > > > http://mdounin.ru/files/ngx_http_upstream_keepalive-0.4.tar.gz
> > > >
> > >
> > > So *either* we use the patch or use the module. Correct?
> >
> > No, to keep backend connections alive you need module *and* patch.
> > Patch provides foundation in nginx core for module to work with
> > fastcgi and http.
> >
> With a custom nginx upstream binary protocol, I believe multiplexing will
> now be possible?
ENOPARSE, sorry.
Maxim Dounin
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx