Hi, I've pretty much adopted the nsopenssl module (especially since I work with folks who are writing code that depends on it) and want to further refactor and simplify it, and want to ask: does ANYONE actually use the libnsopenssl.so stand-alone in their own custom C programs?
I'd like to do away with the libnsopenssl.so and just roll that functionality back into nsopenssl.so, under the (perhaps false) belief that anyone using nsopenssl is using it within AOLserver, and if you're going to use OpenSSL in your C programs, you're going to use the OpenSSL C API directly and not through nsopenssl's libnsopenssl.so. And, since there's no Nsopenssl_Init defined, you can't just [load libnsopenssl.so] from within a Tcl shell and use the Tcl API, either. Considering that the "tls"[1] package already exists, which provides a Tcl binding to the OpenSSL libs, making libnsopenssl.so loadable in a tclsh seems like duplication of effort, except for the slight benefit of providing the same Tcl APIs as you'd have under AOLserver, which might make code reuse slightly easier. I'm not sure if it's worth the mess in the nsopenssl code to keep this /potential/ capability around if no one's actually using it. Thoughts? Comments? Complaints? -- Dossy Footnotes: [1] http://www.flightlab.com/~joe/gutter/doc/tls-1.4/tls.htm -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
