🚀 go-pugleaf

Jonathan Taub <jonathantaub@hotmail.com> wrote in message
news:3c64f657_2@dnews...
> I'm not sure I understand your question.
> There is a method in the Socket class:
>
> public void setSoTimeout(int timeout)
>
> Perhaps this is what you are looking for.
>
Thanks, I knew about that :) No, what I was asking was about graceful ways
of handling timeouts when the socket actually connects (i.e. when the
instance is created). The only advice I have seen so far (in the Javaworld
article I mentioned above) is to create the instance in a seperate thread
(probably an inner class of one's socket wrapper) so that the main thread
can handle any potential timeout without blocking (by default the connection
timeout seems to be a significant amount of time).

The problem with this approach, as I see it, is that if one has a  largish
number of sockets, and they're all timing out when they try to connect, then
you will have a large number of now redundant threads hanging about until
each call to new Socket() returns.

This seems to be unavoidable, barring the possibiltiy of getting an
implementation of SocketImpl with a configurable connection timeout, so my
thoughts have now turned to whether there's any mileage in trying to manage
these background threads in some way to minimise the potential load if
things go wrong.

Cheers for your response,
Owen