| Key: |
HTTPCORE-14
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Oleg Kalnichevski
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
29/Sep/06 08:24 PM
|
|
SocketFactory interface in HttpCore implies a blocking process of opening a new socket. Moreover, there is no way to interrupt the process of opening a connection due to limitations of Java 1.3 API.
I suggest the SocketFactory and SecureSocketFactory interfaces and the Scheme class dependent on those interfaces be moved to HttpConn and the HttpHost class be decoupled from Scheme.
(This is going to be the last controversial bit I wanted to propose and once this issue is resolved I can safely declare I am done with HttpCore)
Oleg
|
|
Description
|
SocketFactory interface in HttpCore implies a blocking process of opening a new socket. Moreover, there is no way to interrupt the process of opening a connection due to limitations of Java 1.3 API.
I suggest the SocketFactory and SecureSocketFactory interfaces and the Scheme class dependent on those interfaces be moved to HttpConn and the HttpHost class be decoupled from Scheme.
(This is going to be the last controversial bit I wanted to propose and once this issue is resolved I can safely declare I am done with HttpCore)
Oleg |
Show » |
|
Consider decoupling HttpHost and Scheme and moving Scheme, SocketFactory and SecureSocketFactory to HttpConn
