Massimiliano Pala wrote:
Sorry, perhaps it is too late but I mean something different. OpenCA::Crypt::OpenSSL::X509 has nothing to do with OpenCA::X509 it is only present to concentrate all X509 relevant C-functions and the Perl-interface for X509-parsing in one seperate module.I would discourage calling C methods within every module because in this way code will not be re-usable (the X509, REQ, etc... cannot remain the same changing the crypto library if we directly call the lib from them ... ).
I try to establish the new modules in the style of OpenSSL. Thea have a cryptoshell (openssl) and every functionality is in a different file (e.g. apps/x509.c). I don't like one big file OpenCA::Crypt::OpenSSL.
Michael
P.S. perhaps I have some time in the evening to read the other mails.
--
-------------------------------------------------------------------
Michael Bell Email (private): [EMAIL PROTECTED]
Rechenzentrum - Datacenter Email: [EMAIL PROTECTED]
Humboldt-University of Berlin Tel.: +49 (0)30-2093 2482
Unter den Linden 6 Fax: +49 (0)30-2093 2959
10099 Berlin
Germany http://www.openca.org
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
