Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: httpclient-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 38005]  - IOWrapper for HttpConnection
In-Reply-To: <bug-38005-13697@http.issues.apache.org/bugzilla/>
Message-Id: <20051229085634.3EAEACB@ajax.apache.org>
Date: Thu, 29 Dec 2005 09:56:34 +0100 (CET)

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


------- Additional Comments From http-async@dubioso.net  2005-12-29 09:56 -------
Hi Peter,

all the tricky parts of a socket are in SocketImpl, which you don't
have to touch. java.net.Socket is a concrete class. You can derive
a new class from it, provide the two or three constructors needed
for the ProtocolSocketFactory, and override getInputStream() and
getOutputStream(). The constructors just pass their arguments to the
respective base class constructor, and possibly perform some additional
initializations for the customized functionality. All in all, this is
hardly more complicated than the interface your patch introduces.

cheers,
  Roland

-- 
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