Hi<div><br></div><div>Could nginx keepalive work with HealthCheck? Does Maxim Dounin have a support plan?</div><div><br></div><div><br></div><div><div><br><div class="gmail_quote">On Wed, Aug 3, 2011 at 3:09 AM, David Yu <span dir="ltr"><<a href="mailto:david.yu.ftw@gmail.com">david.yu.ftw@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Aug 3, 2011 at 2:47 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru" target="_blank">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><br>
On Wed, Aug 03, 2011 at 01:53:30AM +0800, David Yu wrote:<br>
<br>
> On Wed, Aug 3, 2011 at 1:50 AM, Maxim Dounin <<a href="mailto:mdounin@mdounin.ru" target="_blank">mdounin@mdounin.ru</a>> wrote:<br>
><br>
> > Hello!<br>
> ><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" target="_blank">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" target="_blank">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>
> > > > > ><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>
> > ENOPARSE, sorry.<br>
> ><br>
> After some googling ...<br>
> ENOPARSE is a nerdy term. It is one of the standard C library error codes<br>
> that can be set in the global variable "errno" and stands for Error No<br>
> Parse. Since you didn't get it, I can thus conclude that unlike me you are probably<br>
> a normal, well adjusted human being ;-)<br>
<br>
</div></div>Actually, this definition isn't true: there is no such error code,<br>
it's rather imitation. The fact that author of definition claims<br>
it's real error indicate that unlike me, he is normal, well<br>
<div>adjusted human being. ;)<br>
<br>
> Now I get it. Well adjusted I am.<br>
<br>
</div>Now you may try to finally explain what you mean to ask in your<br>
original message. Please keep in mind that your are talking to<br>
somebody far from being normal and well adjusted. ;)<br>
<font color="#888888"><br>
Maxim Dounin<br>
</font><br>
p.s. Actually, I assume you are talking about fastcgi<br>
multiplexing. </blockquote></div></div><div>Nope not fastcgi multiplexing. Multiplexing over a custom/efficient nginx binary protocol.</div><div>Where requests sent to upstream include a unique id w/c the upstream will also send on response.</div>
<div>This allows for asychronous, out-of-bands, messaging.</div><div>I believe this is what mongrel2 is trying to do now ... though as an http server, it is nowhere near as robust/stable as nginx.</div><div>If nginx implements this (considering nginx already has a lot of market share), it certainly would bring more developers/users in (especially the ones needing async, out-of-bands request handling)</div>
<div class="im">
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Short answer is: no, it's still not possible.<br>
<div><div></div><div><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">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></div><br><br clear="all"><div><div></div><div class="h5"><br>-- <br>When the cat is away, the mouse is alone.<br>- David Yu<br>
</div></div><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>
<br></blockquote></div><br></div></div>