I agree with you 100% adn I'm in the same boat. I suggest that if we
can't get people on board that we just go our own way. I'll be happy to
work with you on this and you can reply directly and to the list.
The problem is that at this point IMHO the product is designed to fit into
a client model and only very restrictive server models. I think basically
all we'll need to do is pull the crypto library and the protocol steps out
of the code and rewrite the protocol in a state engine where we simply
keep track of the progress of each connection.
The biggest difficulty I think will be understanding the present
architecture of the project. I've looked inside and what I saw were reams
and reams of code with no internal documentation to speak of. I'm not
trying to critisize the present developers because I think they are doing
a fine job. However I document my code so that 1) others can understand
what I'm up to and take over easily and 2) so after a few years go by if I
need to pick it up again I have some place to start. As I said - when I
looked into OpenSSL I saw no internal docs to speak of.
Anyway, let me know what you think.
Terrell
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
