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 by calling >>> IOControl#suspendInput(), process the request, generate a response, >>> write it out, and finally re-enable input events when ready to receive >>> another request by calling IOControl#requestInput(). >>> >>> >> I assumed this too.. but was wondering that if requests were really >> pipelined (say as a series of GETs), it would be too late to >> suspendInput while processing the first request - I guess I was wrong, >> and the above will work as expected.. >> >> > > It can well happen that multiple pipelined requests end up read into the > session input buffer. As long as the protocol handler does not act upon > that data there should be no problem, though. >
That sounds perfect! many thanks asankha
