> I would like to do the following. Open a connection to an apache server
> using HTTP/1.1 chucking via a POST. Then keep this connection open to
[quoted text clipped - 9 lines]
>
> Thanks in advance
>> ...
>
[quoted text clipped - 3 lines]
> What I would try is probably just to call the servlet every time. That
> makes it probably a bit slower, but more stable.
I was given the requirement that data be streamed via HTTP/1.1
chunking, so making one call to the Servlet for each data segment isn't
an option. Ideally the data would be streamed over a simple TCP
connection, but the client has some firewall constrains that makes the
use of HTTP necessary. Just need to figure out of using Tomcat in this
mode is an option.
ohaya - 02 Sep 2006 17:47 GMT
>>> ...
>>>
[quoted text clipped - 10 lines]
> use of HTTP necessary. Just need to figure out of using Tomcat in this
> mode is an option.
Hi,
It's been awhile since I've looked at it, but doesn't the HTTP POST have
a "Content-length" header that specifies the length of the POST'ed data?
If that is the case, you'd need to know the total byte count of the data
you're going to be POSTing ahead of time, and I think that the webserver
would wait for all of the data per the byte count.
Jim
Andrea Desole - 04 Sep 2006 09:30 GMT
> I was given the requirement that data be streamed via HTTP/1.1
> chunking, so making one call to the Servlet for each data segment isn't
> an option. Ideally the data would be streamed over a simple TCP
> connection, but the client has some firewall constrains that makes the
> use of HTTP necessary. Just need to figure out of using Tomcat in this
> mode is an option.
Never thought of using chunking in a request. Makes kind of sense.
Anyway, the more I think about it the more I have the feeling that the
server wait until the request is complete. It would be nice to know if
it isn't so.