Websockets ... again.

[Bob Sneidar]

If you are going to roll your own security with raw sockets, what I had to do was encrypt the data then base64encode it, then reverse the process on the other side. 

Sent from my iPhone

> On Apr 27, 2024, at 17:56, Richard Gaskin via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Bernard Devlin wrote:
> 
>> One thing to bear in mind is that Livecode does not support secure sockets
>> (despite what the Dictionary might say).
> 
> This is based on the Dictionary example for the "open socket" command. It runs without error, and the callback works. 
> 
>  on mouseup
>     open secure socket to "livecodejournal.com:443"  \
>        with message "wasConnected" without verification
>     put it &cr& the result
>  end mouseup
> 
>  on wasConnected
>     put cr& the params after msg
>  end wasConnected
> 
> 
> I haven't taken the time to craft a more specific test, but perhaps you can describe what you encountered to help guide that.
> 
> --
> Richard Gaskin
> FourthWorld.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode