As Piotr explained, there is no need for threads--it could all be async! In the THttpConnectıonö we need a dynamıc array of requests and when they are storedö we answer them one by one.
Regards, SZ ----- Original Message ----- From: "Francois PIETTE" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Saturday, July 29, 2006 9:20 PM Subject: Re: [twsocket] HTTP/1.1 pipelining--any need? >> How can different threads respond to the same socket?? >> Seems impossible to me. > > As I said: >>> Pipelining use would require changing the state machine in ICS >>> component. > > The change is to clearly separate the execution of the request from the > state machine so that it can be delegated to a thread. > >> If you look at the rfc, the requests are meant to be executed serially. > > The responses must be provided in the same sequence as the requests. This > doesn't mean that each request can't be executed by a separate thread. As > I > said, responses has to be serialized to be sent in the correct order. > > -- > Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html > -- > [EMAIL PROTECTED] > http://www.overbyte.be > > > > ----- Original Message ----- > From: "Fastream Technologies" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Saturday, July 29, 2006 7:23 PM > Subject: Re: [twsocket] HTTP/1.1 pipelining--any need? > > >> ----- Original Message ----- >> From: "Francois PIETTE" <[EMAIL PROTECTED]> >> To: "ICS support mailing" <twsocket@elists.org> >> 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 >>>> HTTP/1.1 >>>> 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. >>> At >>> 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 >>> request >>> 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. >> >> Regards, >> >> SZ >> >>> -- >>> [EMAIL PROTECTED] >>> 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 >> >> -- >> 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 -- 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
