On 29/02/12 10:16, Oleg Kalnichevski wrote:
By the way, is anyone interested in seeing my handlers with (in order)
pipeline support?
Mark
You are also welcome to contribute such implementation to the project,
but ideally in this case it should be consistent with the 4.2 API
Cheers
Oleg
One difficulty with the api is that I don't think a non idempotent
request (e.g. POST) should be sent while there any outstanding responses
in the pipeline. Doing so would make it difficult to identify the cause
of a failure. A failure in one of the pipelined methods ahead of the
post would also result in failure of the POST. However the callback
methods (HttpAsyncRequestProducer.generateRequest,
NHttpRequestExecutionHandler.submitRequest) in both 4.1 and 4.2 api
don't provide any information on the state of any pipeline. So
controlling submission of non idempotent methods has to be done on top
which isn't ideal.
I now have basic pipelining working, but still need to attend to various
error conditions.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
