Methods and Request Timeouts

[Mark R. Diggory]

I've been trying to alter the request timeout period across requests. 
For some requests executed in the client, I want to be able to restict 
the timeout period, for others I really need to have a much longer 
timeout period. This poses a problem, I currently use the 
HttpClient.execute method perform my requests. just setting the timeout 
on the client causes this to be used for all other requests as well.

I need a means, on a request by request basis, to modify the timeout 
period (and still maintain the usage I currently have of the HttpClient 
for connection pooling and status related stuff. Is it possible to use 
HttpConnections out of the ConnectionManager and still have them bound 
to the state of the client (IE Cookies etc).

So far I'm looking at something like:
HttpConnection connection = 
client.getHttpConnectionManager().getConnection(client.getHostConfiguration());
connection.setConnectionTimeout(...)

But, my big concern is that this is again just bleed over into all the 
connections as they are still coming from (and being returned to) a 
pool. Is this a correct assumption?

-Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]