libUrl tsNet and socketTimeoutInterval

Charles Warwick charles at techstrategies.com.au
Thu Dec 7 03:37:09 EST 2017


BR,


> On 7 Dec 2017, at 5:00 am, Sannyasin Brahmanathaswami via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Matthias Rebbe wrote:
> 
>    The connection ID is only used/needed when you use the asynchronous commands of tsNet.   The synchronous commands like tsNetUploadSync or tsNetFileUploadSync or others (they are ending with Sync) do not use connectionIDs. And i assume that put URL and get URL are using the synchronous commands.
>    Matthias
> -------
> OK then…. if we do this:
> 
> 1) tsNetSetTimeouts 60, 3000, 3000 , , 3, 12000
> 
> 2) get url….


At this point, if the speed drops below 12kbps, then the get URL command will return with the result set to indicate failure.


> 
> 3) how do we trap the SocketTimeOut  whose syntax requires a socketID
> 
> from dictionary: 
> 
> Syntax:
> 
> socketTimeout pSocketID
> 
> ?


tsNet does not use standard LiveCode sockets, so socketTimeout does not affect connections using it.

Regards,

Charles

> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list