Best way to handle or disable Pipelined requests

Hi Oleg In the HttoCore Tutorial I see the following "This makes non-blocking HTTP connections fully pipelining capable, but at same time implies that this is the job of the protocol handler to match logically related request and the response messages." Is there any recommended way to handle - o

Re: Best way to handle or disable Pipelined requests

On Sun, 2010-01-24 at 11:25 +0530, Asankha C. Perera wrote: > Hi Oleg > > In the HttoCore Tutorial I see the following > > "This makes non-blocking HTTP connections fully pipelining capable, but > at same time implies that this is the job of the protocol handler to > match logically related reque

Re: Best way to handle or disable Pipelined requests

Hi Oleg > If you do not want to support request pipelining, simply disable input > while processing an incoming message: disable input events immediately > after having received a complete incoming request by calling > IOControl#suspendInput(), process the request, generate a response, > write it o

Re: Best way to handle or disable Pipelined requests

On Mon, 2010-01-25 at 15:16 +0530, Asankha C. Perera wrote: > Hi Oleg > > If you do not want to support request pipelining, simply disable input > > while processing an incoming message: disable input events immediately > > after having received a complete incoming request by calling > > IOControl#

Re: Best way to handle or disable Pipelined requests

Hi Oleg > On Mon, 2010-01-25 at 15:16 +0530, Asankha C. Perera wrote: > >> Hi Oleg >> >>> If you do not want to support request pipelining, simply disable input >>> while processing an incoming message: disable input events immediately >>> after having received a complete incoming request b