Unfortunately, I don't know. In my apps, which tend to be single-user, the maxConnectionsPerHost is usually 2, the HTTP/1.1 recommended number for a single-user agent, (RFC 2616, 8.1.4). I would be very interested to know, however ... as this is important behavior for a proxy representing multiple users. I am sure, though, that an HTTP/1.1 connection will not stay open forever in an unused state; even if the client doesn't close it, any reasonably well behaved and self-preservative server will. So this may be something you need not worry about. Benchmark and see?
On Thu, Oct 16, 2008 at 5:20 PM, Sanjay Acharya <[EMAIL PROTECTED]>wrote: > > Rob, > > Thanks much for your reply. We are moving more in the direction of reusing > the client instance. One question that you might have already dealt with is > how you setup Restlet thus HttpClient to release out connections that have > not been used for a prolonged period of time. Is there a way to enforce an > Idle time out? I do not want to set the "maxConnectionsPerHost" and > "maxTotalConnections" to a small value as that will throttle requests. What > I am hoping to do is set these values large, but in case of a surge of > requests and then have these connections close out after a period of un-use. >
