setReadTimeout() exists since java 1.5 so I guess the right
recommendation would be to use HttpClient if you are still bound to 1.4
Am 07.02.2009 um 02:58 schrieb Marcelo Morales:
It can connect and stall forever. People restart firewalls you know. I
must insist on using at least setReadTimeout(int).
On Fri, Feb 6, 2009 at 3:15 AM, Swinsburg, Stephen
<[email protected]> wrote:
I was just going to do it in a different thread, make a void
function then it can take as long as it needs without having
timeouts. Might still have a timeout just in case though ;)
cheers.
-----Original Message-----
From: Erik van Oosten [mailto:[email protected]]
Sent: Fri 2/6/2009 5:40 AM
To: [email protected]
Subject: Re: making a HTTP request directly in Wicket
Thanks Peter, Marcelo,
Still learning every day...
Regards,
Erik.
Marcelo Morales wrote:
Don't forget setReadTimeout(int)
Also very important.
On Thu, Feb 5, 2009 at 11:42 AM, Peter Ertl <[email protected]> wrote:
Please use commons HttpClient, with the standard Java client you
have no
control over timeouts potentially hanging your application.
Is this still true?
I found that at least in Java 6 there is
URLConnection.setConnectTimeout(int)
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Marcelo Morales
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
