DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34048>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34048

           Summary: Connection reuse with custom HostConfiguration
           Product: HttpClient
           Version: 3.0 Final
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Commons HttpClient
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Connection reuse in MultiThreadedHttpConnectionManager is based on the 
HostConfiguration equality. That is, for two different HostConfiguration 
instances with the same host, port, etc. info the same connection will be 
reused. Right now, because how the code is structured connection reuse is only 
limited to the members of the HostConfiguration class (expect HostParams which 
is not checked in equals() operation). That means if I wanted to extend 
HostConfiguration class with some custom fields that could be used to determine 
if the connection should be reused or not, it won't work because only and 
always the basic HostConfiguration attributes will be checked.
For example, for secure sockets, I would like to specify different security 
properties (e.g. different credentials, integrity vs. privacy, etc.). The 
security properties can be changed between calls and so the existing connection 
for that host must not reused and new must be established. Currently, the 
existing connection would always be reused.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to