[racket] ssl-tcp-unit.rkt restrictions

From: Neil Van Dyke (neil at neilvandyke.org)
Date: Sun Sep 5 19:47:50 EDT 2010

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?

Or, an example practical question: how is one supposed to use SSL 
connection operations with different certificates available each time?

(I don't have an immediate need for this.  At the moment, my project 
requires 4.2.5 and I have to implement certificate support for some 
HTTPS support code that I use with that version.  I'm just looking ahead 
to 5.x, to see whether the project will be able to use 5.x's built-in 
HTTPS support.)


Posted on the users mailing list.