I think I have found a bug in our mobile app…. which is that: If there is poor bandwidth, say, when the user is trying to get a video in the browser widget, or the there is a direct call for other resources from our API (images, audio for player, big XML/Json. etc) the UI hangs. They click a "Go Back" button, but it think that app is trying to (unsuccessufully) process the connection
Now users are typically aware that they have bandwidth issues. For now I don’t want to complicate things by using "tsNetSetTimeouts" to give the user detailed info--maybe in a later version. I just want have them to disconnect as soon as they touch a button, typically a "go back" button. I keep a TSNET api document at my side. I only find two options, as soon as the user says in their mind "I going to bail on this" and hit something, should we use: tsNetclose tsNetLibUrlReuseConnection false ? Any other suggestions on the general architecture to address this scenario will also be appreciated. BR _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
