Richard, thanks for chiming in. 1. dunno, it can't be that hard, i would take an existing implementation in another language and rewrite it in livecode. 2. dunno 3. interesting thought, I will look into testing this. 4. many blockchains are websockets only, and most API with data "streams".
Mike, I hear you on all that. On Fri, Apr 26, 2024 at 7:31 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Tom Glod wrote: > > Can we get a measure again as to the interest in web sockets > implementation > > in livecode? > > Requested 2015, last activity 2020: > https://quality.livecode.com/show_bug.cgi?id=16091 > > Given the elapsed time so far, maybe we can find another way to do this. > > - How hard would it be to script it using LC's good socket support? > > - Is there a curl option available that might allow Charles to handle > this more quickly in tsNet? > > - Would it be feasible to use WebSockets through an embedded browser > widget? > > - What are the use cases requiring WebSockets excluisively? > > - Given the better performance and ligher resource usage for normal > sockets, could > the service host consider supporting normal sockets in addition to > WebSockets? > > > 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
