I would rather see the same effect achieved by using the observable pattern and the HttpFilter interface. The user may choose to keep track of Http response objects received by the filter
I agree. I think this would be better handled more generically by "listening" to the HTTP execution process.
I REALLY like the idea of non-blocking requests. That would be quite a paradigm shift, though. This idea is definitely worth exploring. Could you add a section of this subject to the proposal draft in Wiki?
This is definitely a good idea. This would also be quite useful for pipelining requests.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
