Hi Richard. This email thread now has me curious. If I have an app that starts listening on a port, does that server port have a timeout associated with it that needs refreshing, or does the timeout only exist when a client connects? I have always assumed the latter.
Bob S > On Jun 12, 2024, at 10:26 AM, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Mike Kerner wrote: > >> Richard wrote: >>> Either way, I'd imagine a subscribe client looking to avoid polling >>> is going to depend on a long-lived socket, no? >> >> That's part of the point of a websocket. you don't have to keep >> reopening it, and both ends can use it, as needed. > > Exactly, websockets are useful in browser apps because browsers don't offer > direct socket support. > > LiveCode makes OS-native apps and supports sockets. > > The socketTimeoutInterval lets us set how long they live. > > What am I missing? > > -- > Richard Gaskin > FourthWorld.com > > _______________________________________________ > 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 _______________________________________________ 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
