> From: Chema [mailto:demablo...@gmail.com] > Subject: Re: chunked encoding
> But, if I'm not wrong , chunks messages belong application layer, so > when servers pass them to TCP/IP stack , they are different messages. TCP/IP knows nothing about "messages", only about the two byte streams for the connection (one inbound, one outbound). > Do it by same connection , but they are different messages on > application layer , right ? It's up to the application to deliver the chunks to its outbound TCP/IP stack in the proper order. If you have a multi-threaded application where each thread has responsibility for a different chunk, it's still up to the application to get them to the TCP/IP stack in the correct sequence. However, that is all moot, since the processing of a given request and response in a servlet container is single-threaded, by definition. > I can rely on the order which messages were sent, but it doesn't look > very reliable It's completely reliable, unless you take overt action to write a really, really convoluted application on the server. - 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
