MultithreadedConnectionManager and IdleConnectionTimeoutThread improvements
---------------------------------------------------------------------------
Key: HTTPCLIENT-597
URL: http://issues.apache.org/jira/browse/HTTPCLIENT-597
Project: HttpComponents HttpClient
Issue Type: Improvement
Components: HttpClient
Affects Versions: 3.1 Beta 1
Reporter: Michael Becke
Priority: Minor
Attachments: patch.txt
Changes to MultithreadedConnectionManager and IdleConnectionTimeoutThread
following the suggestions of Balazs SZÜCS.
-------- Forwarded Message --------
From: SZÜCS Balazs <[EMAIL PROTECTED]>
Reply-To: HttpClient User Discussion
<[email protected]>
To: 'HttpClient User Discussion' <[email protected]>
Subject: RE: MultithreadedConnectionManager pooling strategy
Date: Mon, 15 May 2006 15:26:08 +0200
Hello,
I made two changes to the HttpClient code:
1) in the class ConnectionPool in the method getFreeConnection( ... ) I
changed freeConnections.removeFirst() to freeConnections.removeLast(). Now
the container for free connections behaves as a stack rather than a queue.
2) additionally I changed the IdleConnectionTimeoutThread, in the run()
method I added connectionManager.deleteClosedConnections() so that the pool
size is maintained correctly.
What do you think?
Balazs
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
