- From: Yves Lafon <ylafon@w3.org>
- Date: Thu, 21 Sep 2000 18:35:04 +0200 (MET DST)
- To: Thomas Kriegelstein <tk4@irz301.inf.tu-dresden.de>
- cc: www-jigsaw@w3.org
On Mon, 18 Sep 2000, Thomas Kriegelstein wrote:
> Hi
>
> Some time ago, there was a question about a SocketFactory for sockets in
> HttpBasicConnection. And the answer was about a ClientSocketFactory for
> sockets used by clients which use "Jigsaw as an Webserver".
> I think, the original question was about using "Jigsaw as a Proxy" or even
> as a foundation of a webbrowser. (which should be possible according to the
> documentation).
> So as the ingoing sockets in Jigsaw are very easy to be customized
> (Jigsaw-SSL to be mentioned) there is no way, besides editing the Jigsaw
> sources, to have a similar behaviour for outgoing connections (as used in a
> proxy).
>
> And now to my question:
> Is this likely to be changed in an upcoming stable release of Jigsaw this
> year? Is there a chance to have a factory for customized outgoing sockets?
There is already a way to do that, see the HttpMuxConnection and
HttpMuxServer in HttpManager you have a server class, which defaults to
HttpBasicServer.
Would that help or is it not enough for what you want to do?
Regards,
/\ - Yves Lafon - World Wide Web Consortium -
/\ / \ Architecture Domain - Jigsaw Activity Leader
/ \ \/\
/ \ / \ http://www.w3.org/People/Lafon - ylafon@w3.org
Received on Thursday, 21 September 2000 12:35:11 UTC