> From: André Warnier [mailto:a...@ice-sa.com] > Subject: Re: Two way long running servlet connection problem
> In HTTP 1.1, a change was made, with the objective of > avoiding the overhead of establishing/destroying a > connection for each request. Careful here. The "connection" described above is the underlying TCP connection, not the HTTP conversation. > The server reads an processes the request, and sends the response. > The client can now send a second request on the same connection. The scenario the OP wants to discuss is not the simple request/response situation, but more akin to a streaming mechanism, such as a file transfer - but in this case, bidirectional. There's nothing in HTTP that prevents that, as long as appropriate headers are generated so that both the request and response do not have pre-established lengths. > Basically what I mean, is that there is not really a > provision in the webapp logic, for processing a second > request after it has sent a response to the current one. Don't think of it as a second request, but rather as a continuation of the existing one - again, similar to a file transfer over HTTP. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
