[racket] ssl-tcp-unit.rkt restrictions

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.

Jay

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?
>
> 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.)
>
> --
> http://www.neilvandyke.org/
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/users
>



-- 
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://teammccarthy.org/jay

"The glory of God is Intelligence" - D&C 93