Re: libUrl tsNet and socketTimeoutInterval

rename file (Get_Path("Updates")) to > (Get_Path("BackgroundImages")) -- file download complete > > --answer "File'"&&&"has been downloaded. > Result==>" > > else >

Re: libUrl tsNet and socketTimeoutInterval

end DownLoadBackgroundImageComplete - Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Mess

Re: libUrl tsNet and socketTimeoutInterval

end if end if tsNetCloseConn pID end DownLoadBackgroundImageComplete ------------- Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net

RE: libUrl tsNet and socketTimeoutInterval

d if end if tsNetCloseConn pID end DownLoadBackgroundImageComplete - Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-

Re: libUrl tsNet and socketTimeoutInterval

Charles Warwick wrote: Sorry for the confusion, tsNet does handle the ‘load’ function, effectively using its own asynchronous functions to replicate standard libUrl behaviour. BR: wow. That's magic! so this means we can just proceed "as usual" with using load [URL] url [with message

Re: libUrl tsNet and socketTimeoutInterval

Awesome Ralph: Looks like we need to crowd fund Charles for documentation (smile) You are about 3 days ahead of me… can you post some code snippets of your methods? On 12/7/17, 1:54 PM, "use-livecode on behalf of Ralph DiMola via use-livecode"

RE: libUrl tsNet and socketTimeoutInterval

-livecode Sent: Friday, December 08, 2017 5:00 AM To: How to use LiveCode Cc: Charles Warwick Subject: Re: libUrl tsNet and socketTimeoutInterval Hi Ralph, There currently isn’t any ability to query the existing timeout values, though the default values are listed in the dictionary. I will look

Re: libUrl tsNet and socketTimeoutInterval

un...@lists.runrev.com] On Behalf > Of Charles Warwick via use-livecode > Sent: Thursday, December 07, 2017 4:53 PM > To: How to use LiveCode > Cc: Charles Warwick > Subject: Re: libUrl tsNet and socketTimeoutInterval > > Sorry for the confusion, tsNet does handle the ‘load’ functi

RE: libUrl tsNet and socketTimeoutInterval

h DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Charles Warwick via use-livecode Sent: Thursday, December 07, 2017 4:53 PM To: How to use LiveCode Cc: Charles Warwick

Re: libUrl tsNet and socketTimeoutInterval

Sorry for the confusion, tsNet does handle the ‘load’ function, effectively using its own asynchronous functions to replicate standard libUrl behaviour. > On 8 Dec 2017, at 6:44 am, Sannyasin Brahmanathaswami via use-livecode > wrote: > > Thanks Charles…we have

Re: libUrl tsNet and socketTimeoutInterval

Thanks Charles…we have enough to go on now. well, almost if I read you right "load" is not handled by TSNet (since that is libURL's own asynchronous operation?) www.himalayanacademy.com Get the SivaSiva App today (for iPhone and iPad)

Re: libUrl tsNet and socketTimeoutInterval

Sorry, divide my figures for the last parameter to tsNetSetTimeouts by 8, it has been a long day! > On 7 Dec 2017, at 6:33 pm, Charles Warwick > wrote: > > BR, > > >> OK, now going over to the forum on this dropbox thread I see Jacque's and >> Charle's

Re: libUrl tsNet and socketTimeoutInterval

BR, > On 7 Dec 2017, at 5:00 am, Sannyasin Brahmanathaswami via use-livecode > 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

Re: libUrl tsNet and socketTimeoutInterval

BR, > OK, now going over to the forum on this dropbox thread I see Jacque's and > Charle's comments. 5 secs seems a little long.. so if we use the algorithm > "We want to tell users what is up or dim content options from remote servers > in 3 seconds" (and FTP is not in the cards) we get: >

Re: libUrl tsNet and socketTimeoutInterval

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

Re: libUrl tsNet and socketTimeoutInterval

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.

Re: libUrl tsNet and socketTimeoutInterval

Still searching… let's break this down a bit Almost TSNet functions and commands require a connectionID. In some instances these are aribitrary strings assigned by the dev on the initial call, then used later. but what if we use the simple libURL commands? get url

Re: libUrl tsNet and socketTimeoutInterval

Finding answers faster than expected. Spotify seems to want minimum 96kbps. If we use this for our own app/mp3's delivered by CloudFlare -- God only knows it that makes any sense at all… but we have to start somewhere… Now, I'm not super savvy on these units but I think this means 96 X 125

Re: libUrl tsNet and socketTimeoutInterval

@ Charles (and anyone else) using tsNetSetTimeouts 30, 0, 30, 6, 30, 1000 I need to implement this in our app… "minimum amount of data…" is obviously different from "no connection whatsoever" Your example assumes that for this use case, 30 seconds is acceptable. That may well be

Re: libUrl tsNet and socketTimeoutInterval

Hi Ralph, You are correct, as tsNet does not use the standard LiveCode sockets, it does not pay attention to the socketTimeoutInterval. However, rather than disabling tsNet, you can resolve any app hangs related to socket timeouts by using the tsNetSetTimeouts command which allows you to