hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35383] - Provide support for unconnected sockets
Date Mon, 20 Jun 2005 08:23:37 GMT
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=35383>.
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=35383





------- Additional Comments From bchevill.ml@gmail.com  2005-06-20 10:23 -------
That's correct, but as I said it on comment #10, you cannot close the socket
since there is no variable pointing to it. There is no variable because the
creation and the connection of the socket are in the same function.
The workaround is to split the creation and the connection (ie split bind() and
connect()) of the Socket. This way, a pointer to the Socket is returned and you
can call close() on this socket if the thread is blocked, as you said it. As
Oleg said, these changes involve modifying the API, so it marked for release 4.0.

By the way. I don't know how important this bug has been marked (I see P2, but I
don't know what it means), but I think it is very important because this bug
means that you cannot control the behaviour of the client in a real time
environnement (for example you cannot be sure that the client will be closed
immediately).

Benjamin

-- 
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: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message