<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi,<div><br></div><div>This is about using keepalive.</div><div><br></div><div>As I worked on another nginx module, I saw more about 'keepalive'. I see how you have used 'keepalive=1' on 'length == 0' and similar stuff can be seen in memcached module as well. When I was doing the sphinx module I got away with working behavior with the default nginx unbuffered filter because the sphinx service closed the socket after the response and I did not have to play with upstream in_headers to say how much is remaining to read. So it seems if I had to get the advantage of 'keepalive', I need to modify the sphinx service behavior. :-(<br><br>Regards,</div><div>Reetesh<br><br><div><hr id="stopSpelling">From: reeteshr@outlook.com<br>To: nginx-devel@nginx.org<br>Subject: RE: How to implement handshake in an upstream module?<br>Date: Fri, 6 Dec 2013 11:56:41 +0530<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Hi!<div><br><div>> Date: Thu, 5 Dec 2013 13:23:55 -0800<br>> Subject: Re: How to implement handshake in an upstream module?<br>> From: agentzh@gmail.com<br>> To: nginx-devel@nginx.org<br>> <br>> You're essentially doing pipelined requests here and you will run into<br>> the following limitation in the nginx core:<br>> <br>> http://mailman.nginx.org/pipermail/nginx-devel/2012-March/002040.html<br>> <br>> I ran into this when testing my ngx_redis2 module's pipelined request<br>> feature and my patch in that thread will help you :)</div><div><br></div><div>Thanks for the info. :)</div><div><br>> Also, you may also want to deal with keepalive connections in your<br>> module in the future and you will want to save the handshake for<br>> reused connections (from the connection pool).</div><div><br></div><div>Yeah, this is on the table for obvious performance reasons. I saw how you have put that upfront for redis, and that is really good. :)</div><div><br>> <br>> Regards,<br>> -agentzh<br>> <br>> _______________________________________________<br>> nginx-devel mailing list<br>> nginx-devel@nginx.org<br>> http://mailman.nginx.org/mailman/listinfo/nginx-devel<br></div></div> </div>
<br>_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel</div></div> </div></body>
</html>