Alex Tweedly wrote:
> Richard wrote:
>> This excercise raises a question: rather than invent another protocol,
>> why not use HTTP?
>
>
> Usually, because HTTP is quite decidedly a client-server protocol.
> If you have a peer-peer protocol need, then you have to bend HTTP
> out of shape :-)
Soc
On 25/02/2025 19:49, Bob Sneidar via use-livecode wrote:
Because I developed my own encryption API which uses AES256 but has a couple
tricks. SSL certs will not suffice, and the whole point to having my own
encryption technique is so that I can avoid SSL certs and the process of
registering
I played around with this last night, and determined that the length does not
have to be sent, the receiving process can simply keep reading for n
characters, appending the data to a low level file in a repeat loop until the
it variable is empty. I tried this and the entire payload was received.
Because I developed my own encryption API which uses AES256 but has a couple
tricks. SSL certs will not suffice, and the whole point to having my own
encryption technique is so that I can avoid SSL certs and the process of
registering them and installing them.
Because I am encrypting the file
Hi!
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
On Thu, Jan 23, 2025 at 21:09 J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Anyone who cut their teeth on HyperCard is old now.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Soft
Bob Sneidar wrote:
> I played around with this last night, and determined that the length does
> not have to be sent, the receiving process can simply keep reading for n
> characters, appending the data to a low level file in a repeat loop until
> the it variable is empty. I tried this and the ent
