[squeak-dev] [ANNOUNCE] ParrotTalk release/design change considerations

Denis Kudriashov dionisiydk at gmail.com
Fri Nov 17 14:41:37 UTC 2017


Hi Henry.
I decided to ask this questions here.

What the advantage to use your security solution instead of legacy secure
sockets which is available in the image? (implemented with
ZdcSecureSocketStream)

2017-10-24 18:33 GMT+02:00 henry <henry at callistohouse.club>:

> Hi all,
>
> I am happy to announce the release of version 3.5 of ParrotTalk, for
> Squeak and Pharo, found here:
>
> http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz
>
> It follows this specification:
> https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/
> ParrotTalkFrameDesign-3.5.pdf
>
> One item of note, in version 3.5, the system connecting to a server,
> sending the IWant msg, must know the vatId of the system being connected
> to. I am considering changing this to version 3.6 by removing one
> round-trip in messaging. Therefore, these messages would be combined:
> IWant/GiveInfo, IAm/ReplyInfo. I will keep ProtocolOffered and
> ProtocolAccepted to allow eLindaSession to support both versions: 3.5 and
> 3.6.
>
> Thoughts please?
>
> - HH
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20171117/8c729c8e/attachment.html>


More information about the Squeak-dev mailing list