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
libURL now using tsNet is a great addition to v8 but it seems to have broken my
code without warning unless I missed this warning in the release notes. I seems
that when tsNet was included in v8 the property socketTimeoutInterval does
nothing when doing ==> put url("https://"&":") into tWebData
We have had this discussion multiple times, on both this list and in the
forums, if memory serves.
On Wed, Nov 22, 2017 at 3:32 AM, Pyyhtiä Christer via use-livecode <
use-livecode@lists.runrev.com> wrote:
> It might be this discussion has already been on this list.
>
> Recently I have seen and
It might be this discussion has already been on this list.
Recently I have seen and heard future views on the time of apps running in the
users' devices getting past in a few years. This means the apps run in servers
and use standard browsers running HTML5 and an efficient language snippets
