Hi All, I would really like to get more details here. The windows specific code is part of the SqueakSSL design. The idea is that each platform uses a native TLS implementation instead of using custom thrown code. If the Windows implementation is using non windows code, then what is it using for TLS? We are using SqueakSSL in production code. It works communicating between linux servers, and windows and mac clients. I would be interested not only in details but also in benchmarks. Ron

From: vm-dev-bounces@lists.squeakfoundation.org [mailto:vm-dev- bounces@lists.squeakfoundation.org] On Behalf Of Frank Shearar Sent: Monday, March 18, 2013 2:38 PM

On 12 March 2013 01:55, <commits@source.squeak.org> wrote:

...

David T. Lewis uploaded a new version of VMMaker to project VM Maker: http://source.squeak.org/VMMaker/VMMaker-dtl.304.mcz

==================== Summary ====================

Name: VMMaker-dtl.304 Author: dtl Time: 11 March 2013, 9:54:49.662 pm UUID: 7381d88a-6574-4f47-9a1e-ad72ddc48520 Ancestors: VMMaker-dtl.303

VMMaker 4.10.14

Reference Mantis 0007751: Add SSL plugin Add Andreas Raab's SqueakSSLPlugin to the update map for source.squeak.org/VMMaker. Add SqueakSSLPlugin to the VMMakerTool defaultUnixSpec.

Follow up required: Add platform sources to SVN from Andreas'

respository at http://code.google.com/p/squeakssl for from the oscog branch.

...

=============== Diff against VMMaker-dtl.303 ===============

I asked on the Pharo-dev mailing list about their SSL plugin; it seems it's SqueakSSL with the Mac- and Windows-specific stuff ripped out. Any chance of the various VM folk getting the same plugin in all the various VMs so we don't diverge unnecessarily?

frank