DO NOT REPLY [Bug 31322] New: - SO Timeouts should be finer grained

[bu...@apache.org]

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=31322>.
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=31322

SO Timeouts should be finer grained

           Summary: SO Timeouts should be finer grained
           Product: Commons
           Version: 2.1 Final
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: HttpClient
        AssignedTo: commons-httpclient-dev@jakarta.apache.org
        ReportedBy: ghexsel@uol.com.br


I'm using HttpClient in multithreaded mode, and I'm not able to set the
connection timeouts on a per-user base, it's an everyone-the-same setting for
the client.

Our project implements searching and parsing of multi-step wizards
(meta-searching other search engines), and we have a general timeout for the
whole process.  Unfortunately, with HttpClient, I can't set the timeout on a
per-method (HttpMethod I mean) basis.  And I can't access the socket either,
which would provide some kind of work-around.  Any work-arounds you know, short
of spawning a new HttpClient for each step?

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org