atom feed75 messages in ru.sysoev.nginxRe: upstream keepalive - call for tes...
FromSent OnAttachments
Maxim DouninAug 1, 2011 9:07 am 
liseenAug 2, 2011 6:36 am 
António P. P. AlmeidaAug 2, 2011 8:24 am 
Maxim DouninAug 2, 2011 10:32 am 
Maxim DouninAug 2, 2011 10:35 am 
David YuAug 2, 2011 10:41 am 
Maxim DouninAug 2, 2011 10:49 am 
David YuAug 2, 2011 10:52 am 
Maxim DouninAug 2, 2011 11:46 am 
David YuAug 2, 2011 12:09 pm 
卫越Aug 2, 2011 7:48 pm 
liseenAug 2, 2011 8:56 pm 
SplitIceAug 2, 2011 10:20 pm 
Maxim DouninAug 3, 2011 12:37 am 
Charles ChenAug 3, 2011 2:18 am 
Matthieu TourneAug 3, 2011 5:06 pm 
Maxim DouninAug 3, 2011 11:51 pm 
SplitIceAug 7, 2011 9:43 pm 
Maxim DouninAug 8, 2011 2:21 am 
SplitIceAug 8, 2011 2:34 am 
SplitIceAug 8, 2011 2:35 am 
Matthieu TourneAug 12, 2011 12:32 pm.patch, .patch
Maxim DouninAug 12, 2011 12:59 pm 
Matthieu TourneAug 12, 2011 2:11 pm 
Maxim DouninAug 12, 2011 3:26 pm 
Matthieu TourneAug 12, 2011 3:41 pm.patch
Matthieu TourneAug 16, 2011 4:29 pm 
Maxim DouninAug 16, 2011 5:21 pm 
magicbearAug 24, 2011 10:11 am 
Maxim DouninAug 24, 2011 5:04 pm.txt, .txt
Shaun savageAug 24, 2011 6:16 pm 
magicbearAug 24, 2011 10:30 pm 
magicbearAug 26, 2011 12:07 am 
Maxim DouninAug 26, 2011 2:38 am 
magicbearAug 26, 2011 4:00 am 
magicbearAug 26, 2011 4:04 am 
magicbearAug 26, 2011 4:27 am 
Maxim DouninAug 26, 2011 4:36 am 
magicbearAug 26, 2011 4:53 am 
Maxim DouninAug 26, 2011 8:54 am 
magicbearAug 26, 2011 9:16 am 
magicbearAug 26, 2011 9:27 am 
magicbearAug 26, 2011 10:00 am 
magicbearAug 26, 2011 10:51 am 
Maxim DouninAug 26, 2011 11:05 am 
magicbearAug 26, 2011 12:00 pm 
magicbearAug 28, 2011 10:06 am 
magicbearAug 28, 2011 10:10 am 
Maxim DouninAug 28, 2011 6:46 pm.txt
magicbearAug 31, 2011 1:04 pm 
SplitIceAug 31, 2011 6:56 pm 
magicbearSep 1, 2011 6:37 am 
magicbearSep 4, 2011 10:33 am 
Maxim DouninSep 4, 2011 11:20 am 
MagicBearSep 4, 2011 11:31 am 
Maxim DouninSep 5, 2011 12:07 am 
ビリビリⅤSep 5, 2011 8:41 am 
Maxim DouninSep 5, 2011 11:01 am 
magicbearSep 5, 2011 11:39 pm 
Matthieu TourneSep 7, 2011 4:33 pm 
Maxim DouninSep 8, 2011 2:26 am 
Maxim DouninSep 8, 2011 8:41 am 
Matthieu TourneSep 8, 2011 3:04 pm 
magicbearSep 14, 2011 3:53 pm 
MagicBearSep 15, 2011 10:50 am.txt
SplitIceSep 15, 2011 6:41 pm 
philippDec 29, 2011 4:46 am 
Maxim DouninDec 29, 2011 7:03 am 
alexscottMar 8, 2012 6:29 am 
Andrew AlexeevMar 8, 2012 10:17 pm 
alexscottMar 12, 2012 7:34 am 
Maxim DouninMar 12, 2012 7:53 am 
alexscottMar 12, 2012 10:39 am 
Maxim DouninMar 12, 2012 10:58 am 
alexscottMar 12, 2012 12:55 pm 
Subject:Re: upstream keepalive - call for testing
From:David Yu (davi@gmail.com)
Date:Aug 2, 2011 12:09:10 pm
List:ru.sysoev.nginx

On Wed, Aug 3, 2011 at 2:47 AM, Maxim Dounin <mdou@mdounin.ru> wrote:

Hello!

On Wed, Aug 03, 2011 at 01:53:30AM +0800, David Yu wrote:

On Wed, Aug 3, 2011 at 1:50 AM, Maxim Dounin <mdou@mdounin.ru> wrote:

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 <mdou@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, mdou@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.

After some googling ... 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. Since you didn't get it, I can thus conclude that unlike me you are probably a normal, well adjusted human being ;-)

Actually, this definition isn't true: there is no such error code, it's rather imitation. The fact that author of definition claims it's real error indicate that unlike me, he is normal, well adjusted human being. ;)

Now I get it. Well adjusted I am.

Now you may try to finally explain what you mean to ask in your original message. Please keep in mind that your are talking to somebody far from being normal and well adjusted. ;)

Maxim Dounin

p.s. Actually, I assume you are talking about fastcgi multiplexing.

Nope not fastcgi multiplexing. Multiplexing over a custom/efficient nginx binary protocol. Where requests sent to upstream include a unique id w/c the upstream will also send on response. This allows for asychronous, out-of-bands, messaging. 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. 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)

Short answer is: no, it's still not possible.

_______________________________________________ nginx mailing list ngi@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

-- When the cat is away, the mouse is alone. - David Yu

_______________________________________________ nginx mailing list ngi@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx