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=28322>. 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=28322 Connection timeout logic redesign Summary: Connection timeout logic redesign Product: Commons Version: 2.0 Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: HttpClient AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Changelog: * CreateSocket method with timeout parameter added to the ProtocolSocketFactory interface * TimeoutController related code factored out of HttpConnection class and moved into ControllerThreadSocketFactory helper class * ReflectionSocketFactory helper class added. This factory encapsulates reflection code to call JDK 1.4 Socket#connect method if supported * All protocol socket factories now attempt to initially use ReflectionSocketFactory if required to create a socket within a given limit of time. If reflection fails protocol socket factories fall back onto the good ol' ControllerThreadSocketFactory Benefits: * HttpConnection code got a lot cleaner * When running in modern JREs expensive timeout controller thread per connection attempt is no longer needed * Ugly code intended to work around limitations of the older JREs is now confined to a few helper classes that can be easily thrown away once we move onto Java 1.4 Let me know what you think Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
