I have (what appears to me at) a fairly straight-forward approach: allow HttpConnectionParams to be created and customized before physical HttpConnection instance is allocated, when connection manager allocates a connection it can look corresponding parameter object up from a hash map, and, if found, assign it to the connection. End of the story.
With the intent to clarify my previous suggestions: this could be the right
approach, for setting a timeout on a per-method base is actually a workaround
as Oleg pointed out. A control on the HttpConnecction level would be more suitable. But, if I understand well your intent here and the global httpclient architecture, tieing the customization of HttpConnectionParams to a specific HostConfiguration would prevent different method execution attempts on a host from having different (increasing) timeouts.. Am I missing something?
Cheers Fabio
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
