getting timeout with load URL
Phil Davis
revdev at pdslabs.net
Wed Feb 25 12:38:08 EST 2009
Hi Jim and others,
My comment here moves us away from the original issue a bit, but...
As far as I can tell, the socketTimeoutInterval doesn't seem to interact
with the 'load' command. At least, the 'socketTimeout' message isn't
sent when 'load' exceeds the socketTimeoutInterval. That's my
experience. Am I missing something?
Thanks -
Phil Davis
(re-sent because original went into 'moderation' queue due to size)
Jim Bufalini wrote:
> Hi Tiemo,
>
> It's probably not a Rev issue but a machine specific issue. Please do a
> Google search on "socket keepalive windows." (keepalive is one word)
> Something on that machine is set wrong. You'll find a lot of information on
> this topic and what to look for on the machine. As far as Rev goes, the
> socketTimeOutInterval is all you normally have to adjust.
>
> Jim Bufalini
>
>
>> -----Original Message-----
>> From: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
>> bounces at lists.runrev.com] On Behalf Of Tiemo Hollmann TB
>> Sent: Wednesday, February 25, 2009 6:50 AM
>> To: 'How to use Revolution'
>> Subject: AW: getting timeout with load URL
>>
>> Hi Jim,
>> yes, I have followed this excellent roadbook from Eric and everything
>> works
>> fine so far. Up to now, where one beta tester got these mysterious
>> timeouts
>> (which I verified with URLStatus()). So it isn't a general problem, but
>> seems to be an issue on his PC (Win XP) or his Provider line. I was
>> wondering if there are other settings as the socketTimeoutInterval I
>> can
>> control from Rev or if I have to take it as it is?
>> Thank you
>> Tiemo
>>
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
>>> bounces at lists.runrev.com] Im Auftrag von Jim Bufalini
>>> Gesendet: Mittwoch, 25. Februar 2009 17:32
>>> An: 'How to use Revolution'
>>> Betreff: RE: getting timeout with load URL
>>>
>>> Hi Tiemo,
>>>
>>> Would you go here:
>>>
>>> http://www.sosmartsoftware.com/?r=revolution_didacticiels&l=en
>>>
>>> and down to tutorial #018 How to download data from the Internet.
>>>
>> Download
>>
>>> the tutorial. Everything you need to know should be there including
>>>
>> using
>>
>>> the load command.
>>>
>>> Jim Bufalini
>>>
>>>
>>>> -----Original Message-----
>>>> From: use-revolution-bounces at lists.runrev.com [mailto:use-
>>>>
>> revolution-
>>
>>>> bounces at lists.runrev.com] On Behalf Of Tiemo Hollmann TB
>>>> Sent: Wednesday, February 25, 2009 6:28 AM
>>>> To: 'How to use Revolution'
>>>> Subject: AW: getting timeout with load URL
>>>>
>>>> I tried it with setting the socketTimeoutInterval to 20000 and even
>>>> 30000
>>>> before the load url, but this guy still gets a timeout at most
>>>> attempts.
>>>> After 5-10 retries he can download the file of about 4MB.
>>>>
>>>> Any other tweak or any other idea, what could be going on here and
>>>> where to
>>>> look for?
>>>>
>>>> Thanks for any ideas
>>>> Tiemo
>>>>
>>>>
>>>>
>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: use-revolution-bounces at lists.runrev.com [mailto:use-
>>>>>
>> revolution-
>>
>>>>> bounces at lists.runrev.com] Im Auftrag von Klaus Major
>>>>> Gesendet: Mittwoch, 25. Februar 2009 11:52
>>>>> An: How to use Revolution
>>>>> Betreff: Re: getting timeout with load URL
>>>>>
>>>>> Hi Tiemo,
>>>>>
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am experiencing sometimes timeouts with a load URL at a beta
>>>>>>
>>>> tester.
>>>>
>>>>>> Testing the same download from same server at the same time,
>>>>>>
>> runs
>>
>>>>>> smooth.
>>>>>> Obviously the bottleneck seems to be the internet connection or
>>>>>> provider of
>>>>>> the tester, though he is supposed to have a 2000 kBit line. On
>>>>>>
>> the
>>
>>>>>> other
>>>>>> hand he can surf the net and downloads mails without a problem
>>>>>>
>> -
>>
>>>>>> beside of
>>>>>> slow performance some times.
>>>>>>
>>>>>> Are there any options to tweak the load URL / internet
>>>>>>
>> connection
>>
>>>> from
>>>>
>>>>>> within Rev, like setting the timeout, retrying or anything
>>>>>>
>> else? Or
>>
>>>>>> do I
>>>>>> just have to live with that behaviour and have to tell my
>>>>>>
>> customers
>>
>>>> to
>>>>
>>>>>> retry?
>>>>>>
>>>>>> Thanks for any experience
>>>>>>
>>>>> you can get and set "the socketTimeOutInterval" like:
>>>>> ...
>>>>> put the socketTimeOutInterval into alt_interval
>>>>> set the socketTimeOutInterval to 20000
>>>>> ## Do your internet stuff...
>>>>> set the socketTimeOutInterval to alt_interval
>>>>> ...
>>>>>
>>>>> that's the way we do it and it works fine so far :-)
>>>>>
>>>>>
>>>>>> Tiemo
>>>>>>
>>>>> Best
>>>>>
>>>>> Klaus
>>>>>
>>>>> --
>>>>> Klaus Major
>>>>> klaus at major-k.de
>>>>> http://www.major-k.de
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
More information about the use-livecode
mailing list