.
Date: Thu, 6 Jan 2011 12:12:37 -0500
From: ch...@christopherschultz.net
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
On 1/5/2011 4:29 PM, ilya goberman wrote:
I
:
maxKeepAliveRequests=1 in server.xml
Date: Thu, 6 Jan 2011 16:08:36 -0500
From: ch...@christopherschultz.net
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
On 1/6/2011 12:27 PM, ilya
Got it, thanks
Date: Thu, 6 Jan 2011 16:34:40 -0500
From: ch...@christopherschultz.net
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
On 1/6/2011 4:17 PM, ilya
, ilya goberman wrote:
Hi,
I use NIO HTTP Tomcat connector org.apache.coyote.Http11NioProtocol to
implement Comet streaming to browsers and mobile devices.
I would like to disable HTTP response chunked encoding to reduce bandwidth.
How significant is the overhead with chunking in your
Hi,
I am trying to use NIO HTTP Tomcat connector
org.apache.coyote.Http11NioProtocol to implement Comet streaming to browsers
and mobile devices (using Tomcat org.apache.catalina.comet.CometProcessor).
The application opens a persistent Comet connection to receive data from the
server.
a tcp connection and creating a new one?
Because you are removing the benefits of keep-alive here.
Compare that with sending 6 extra bytes in a IP-packet that you are sending
anyway.
Ronald.
Op woensdag, 5 januari 2011 16:29 schreef ilya goberman gober...@msn.com:
Mark
From: ma...@apache.org
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
On 05/01/2011 15:29, ilya goberman wrote:
Mark, overhead of chunked encoding can be significant. My typical message
is about 50 bytes and chunked
OK, it is fair, thanks.
Date: Wed, 5 Jan 2011 17:54:53 +
From: ma...@apache.org
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
On 05/01/2011 17:43, ilya goberman wrote:
Mark,
1) TCP/IP overhead? Not sure why you
is not
set, keep alive functionality is preserved.
Any objections?
Date: Wed, 5 Jan 2011 17:54:53 +
From: ma...@apache.org
To: users@tomcat.apache.org
Subject: Re: How to disable chunked encoding for the Http11NioProtocol
connector.
On 05/01/2011 17:43, ilya goberman wrote:
Mark,
1
This is getting philosophical. spec-respectful does not mean it has to
support only one valid protocol out of 2. If both protocol A (chunked-encoding)
and B (no chunked encoding) is allowed, why not give an ability to use whatever
user prefers.
As far as sputnik example is concerned, I have
Hi,
I use NIO HTTP Tomcat connector org.apache.coyote.Http11NioProtocol to
implement Comet streaming to browsers and mobile devices.
I would like to disable HTTP response chunked encoding to reduce bandwidth.
The response will have header Connection: close with Content-Length header
omitted.
11 matches
Mail list logo
