IHttpAsyncHandler & Request/Response Serialization...

[Nikos Konstas]

Hi,

I'm implementing a simple protocol on top of HTTP using asynchronous
http handlers. Session state is disabled so multiple requests from the
same client can be processed concurrently.

I want to keep the number of client connections to an absolute minimum
(i.e. one connection per client). To achieve that I need to be able to
process requests from clients as they arrive even if they already have
outstanding requests.

The problem I have is that if I send multiple requests using the same
physical connection then they are serialized: request N+1 will be handed
once the processing for request N has been completed.

Is there a way to handle requests as they arrive? I suspect that IIS
enforces this serialization - is it possible to turn it off?

Thank you,
Nikos.

 

[John Saunders [MVP]]

Hi,

I'm implementing a simple protocol on top of HTTP using asynchronous http
handlers. Session state is disabled so multiple requests from the same
client can be processed concurrently.

I want to keep the number of client connections to an absolute minimum
(i.e. one connection per client). To achieve that I need to be able to
process requests from clients as they arrive even if they already have
outstanding requests.

The problem I have is that if I send multiple requests using the same
physical connection then they are serialized: request N+1 will be handed
once the processing for request N has been completed.

Is there a way to handle requests as they arrive? I suspect that IIS
enforces this serialization - is it possible to turn it off?

I don't believe that IIS does any serialization. Are you sure that request
N+1 is sent before request N has completed? Have you looked at the network
traffic and confirmed this?