LC just provides raw sockets. You can implement a TLS equivalent with a bit of elbow grease. Writing your own protocol gives a lot of control.
TLS is something you may have to use to check boxes. Out of curiosity is there a market for something like this within the community? Sent from my iPhone > On Apr 27, 2024, at 6:30 PM, Mike Kerner via use-livecode > <use-livecode@lists.runrev.com> wrote: > > really? discuss. > >> On Sat, Apr 27, 2024 at 5:06 PM Bernard Devlin via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> One thing to bear in mind is that Livecode does not support secure sockets >> (despite what the Dictionary might say). >> On Sat, Apr 27, 2024 at 12:31 AM Richard Gaskin via use-livecode < >> use-livecode@lists.runrev.com> wrote: >>> - How hard would it be to script it using LC's good socket support? >>> 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 > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > 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
