Hi Bahaa,

Bahaaldin Al-amood wrote:

I am currently working on the LunaCA3 module, I keep running into this
OpenCA::OpenSSL module but I can not see where this module is located on
the file system; here is the output of ls in the modules directory

This module include C-code. Therefore it is placed in the platform dependent area of perl (perl5/i386-linux or something like this).


and if it is under OpenCA::Token then why is it not used as such?

OpenCA::Token::OpenSSL is a different module.

another thing what is the AUTOLOAD ? and why is it called in a loop? (I
do not know exactly if that is right) but is being called thousands of
times when I try to start the server ( I put a print statement and the
beginning of sub AUTOLOAD in OpenCA::Token::LunaCA3) to see how many
times it is being called.

AUTOLOAD is used if a function is not implemented by this module. Sometimes it is not necessary that a module implements every function. We use AUTOLOAD to forward such function calls to the OpenSSL module directly. Perhaps you can compary the AUTOLOAD function with the one in the nCipher module.


BTW. I forget the guy from nCipher completely. I hope he is not totally frustrated.

Michael
--
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6
[EMAIL PROTECTED]   D-10099 Berlin
_______________________________________________________________


------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ OpenCA-Devel mailing list OpenCA-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to