Hello Howard,
Check the socketTimeoutInterval in the docs. This property allows you
to increase time before the request for the url times out.
Rev continues to run a handler after the get/put url command
terminates. It terminates either because it has read all available
data or because it times out.
Best,
Mark
--
Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Convert HyperCard stacks with DIFfersifier. Download it at http://
differsifier.economy-x-talk.com
Op 23-aug-2006, om 23:02 heeft Howard Bornstein het volgende geschreven:
I'm using Get URL <url> to access a web page. Sometimes that page
comes back
blank. I assume it's because the request timed out before the page
contents
was delivered. In this case it's fine because I'm testing to see if
the page
is up and responding. But what determines how much time it takes
before Rev
returns with blank data as opposed to the contents of the web page?
The docs on URL say:
"All actions that refer to a URL container are blocking: that is, the
handler pauses until Revolution is finished accessing the URL. Since
fetching a web page may take some time due to network lag,
accessing URLs
may take long enough to be noticeable to the user."
So if getting the URL is a blocking activity, why does Rev go on at
all if
nothing is returned? Is there a way to set the amount of time Rev
will wait
before timing out?
--
Regards,
Howard Bornstein
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
