You caught, me, I was just thinking out loud, because i always have
it WAITFORRESULT.
but if you setup a quick test page that you ping with the test url
Ben
On Jul 21, 2006, at 1:42 PM, John McGowan wrote:
i didn't think you'd get any results if you told it not to wait for a
result....
Have you actually done this, or are you just assuming that the
detailed response will say something useful about the fact that no
connection was made?
Ben Johansen wrote:
the only thing i can think of is to run a smaller @url test with
these settings
WAITFORRESULT=false
DETAILEDRESPONSE=true
and check the response
Ben
On Jul 21, 2006, at 1:22 PM, John McGowan wrote:
Is there some way of changing the timeout for an @URL call. I need
to add some error handling to my code, but if the server at the
other end is down, @URL takes forever to give up.
/John
--
John McGowan
[EMAIL PROTECTED]
P 847.608.6900 x 110
F 847.608.9501
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
--
John McGowan
[EMAIL PROTECTED]
P 847.608.6900 x 110
F 847.608.9501
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
