----- Original Message -----
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing" <email@example.com>
Sent: Saturday, July 29, 2006 6:17 PM
Subject: Re: [twsocket] HTTP/1.1 pipelining--any need?
>> I wonder the optional RFC2616 pipelining mechanism for requests in
>> is anything utilized by clients in the real world or just hypothetical?
>> Currently no ICS code (client/server) supports it.
> Pipelining use would require changing the state machine in ICS component.
> first glance I don't think it is too much difficult to implement. But
> performance would be enhanced only when using threads to serve each
> in the HTTP server component. The thread has to be used not for the entire
> client instance but for HTTP request processing only so that pipelining
> could start different threads to execute each request. Of course
> serialization would be necessary to send the results in the correct order.
How can different threads respond to the same socket?? Seems impossible to
me. If you look at the rfc, the requests are meant to be executed serially.
> Is there any client which make use of pipelining ? I doubt !
I do not know any neither! That's why I felt the need to ask here.
> [EMAIL PROTECTED]
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be