[racket] ssl-tcp-unit.rkt restrictions

From: Neil Van Dyke (neil at neilvandyke.org)
Date: Mon Sep 6 12:24:53 EDT 2010

Thanks, Jay.

I haven't looked thoroughly yet, but I suspect that simply moving the 
SSL client context object from a hidden variable to a public parameter 
would be a small change that's a lot more flexible.

I'm working with the old PLT 4.2.5 "openssl" code early this week, so I 
might soon be begging for more or different enhancements in 5.x.

Jay McCarthy wrote at 09/06/2010 12:07 PM:
> I doubt there is a good reason for these restrictions. I imagine that
> it works this way because it is only used by a few people and this is
> all they needed. IIRC, only the hand-in server uses it in the tree.
> I'm happy to work with you to improve it, if I understood what exactly
> you wanted.

> On Sun, Sep 5, 2010 at 5:47 PM, Neil Van Dyke <neil at neilvandyke.org> wrote:
>> Why does the 5.0.1 "ssl-tcp-unit.rkt" hide the SSL client context and
>> require all the certificates and such to be provided at unit invocation(?)
>> time?


Posted on the users mailing list.