Name: rm29839 Date: 12/08/97
It looks like SOCKS support, at least in the JDK1.1.3,
is supported by settign system properties that
describe the location of the SOCKS proxy. These
are examined by PlainSocketImpl.java in the JDK
implementation.
This means that if I set these properties, they
will be used for *all* connections that my application
makes, even to my local host. That's no good.
It would be much better if I could implement some
interface, say, SocksDirector. If I have a class
that implements this interface, I could tell the
Socket-level code about it, and each time it's
about to make a connection, it could query my class
to see what socks host/port to use for this connection,
if any.
(Review ID: 21381)
======================================================================
###@###.### 10/29/04 18:22 GMT
It looks like SOCKS support, at least in the JDK1.1.3,
is supported by settign system properties that
describe the location of the SOCKS proxy. These
are examined by PlainSocketImpl.java in the JDK
implementation.
This means that if I set these properties, they
will be used for *all* connections that my application
makes, even to my local host. That's no good.
It would be much better if I could implement some
interface, say, SocksDirector. If I have a class
that implements this interface, I could tell the
Socket-level code about it, and each time it's
about to make a connection, it could query my class
to see what socks host/port to use for this connection,
if any.
(Review ID: 21381)
======================================================================
###@###.### 10/29/04 18:22 GMT
- duplicates
-
JDK-4894482 Tiger PIT: Incorrect socks setting will cause JPI/JWS fail to launch Java app
-
- Closed
-
-
JDK-4697272 HttpClient should fall back to connecting locally if rejected by instProxy
-
- Closed
-