How to restrain impatient tsNet?
rdimola at evergreeninfo.net
Mon Nov 8 12:44:20 EST 2021
One more thing. Function GetNetworkType below will return the network type. The handler NetworkType will report the status and version.
if GetNetworkType() = "Sockets" then
answer "tsNet is disabled"
answer "tsNet in use. Version==>"& tsNetVersion()
put the behavior of stack"revLibUrl" into tLibUrlDriver
if tLibUrlDriver is empty then
Evergreen Information Services
rdimola at evergreeninfo.net
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Ben Rubinstein via use-livecode
Sent: Sunday, November 07, 2021 4:55 PM
To: use-livecode at lists.runrev.com
Cc: Ben Rubinstein
Subject: Re: How to restrain impatient tsNet?
Thanks Mark and Matthias!
On 07/11/2021 19:28, matthias rebbe via use-livecode wrote:
> i am not sure if you are already aware of this, but in case you ever want to test your app without tsNet in LC 9.5.x or higher or you want to create it with LC 9.5.x or higher but without using tsNET you could unload tsNet in LC IDE before testing or creating the standalone. LC then uses only the 'standard' libUrl library.
> To disable tsNET execute this in the message box
> dispatch "revunloadlibrary" to stack tsnetliburl
> Please keep in mind that you have to unselect tsNet in the Inclusions section of the standalone builder in case you've set the standalone settings to manually select the inclusions.
> To enable tsNET again execute this in the message box
> dispatch "revloadlibrary" to stack tsnetliburl
>> Am 07.11.2021 um 18:50 schrieb Mark Waddingham via use-livecode <use-livecode at lists.runrev.com>:
>> I think tsNetSetTimeouts is what you need :)
>> Warmest Regards,
>> Sent from my iPhone
>>> On 7 Nov 2021, at 16:51, Ben Rubinstein via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> I'm finally moving an app from LC 6.7 to LC 9.6.5 (huge thanks to Mark W for fixing the accumulating/sorting delay loops, which has made this possible).
>>> I've hit what I hope is the last hurdle: at one point in its processing, the app has to load a resource over HTTP, which is s.l.o.w. - it typically takes around 8 minutes at the moment.
>>> By setting the sockettimeoutinterval to the extreme 1800 (i.e. half an hour) this has been fine.
>>> But under 9.6.5, in spite of this setting, it craps out within a minute with the message
>>> tsneterr: (28) Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds
>>> Does tsneterr ignore the sockettimeoutinterval? Is there some other property I can set to persuade it to be patient?
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode