> Lundgren, Scott wrote: > > Hey All, > > > > I've had time to revisit my issue with Crypt::SSLeay & IIS using the > > suggestions from this mailing list. In short, none of them > solved it. > > The problem I'm having is Crypt::SSLeay is installed on IIS > 6.0 but the > > script I'm using doesn't believe that the module is installed. I'd > > really like to solve this problem, what other resources or > mailing lists > > would you suggest (and no there is no budget for a support > contract with > > ActiveState) ? > > > > One thing that puzzles me from that earlier correspondence is > how come > $^X, which is C:/perl/bin/perl.exe (when the script is > executed from the > command line), becomes C:/perl/bin/perlis.dll (when the script is > executed from the browser). Is this normal IIS behaviour ? What is > 'perlis.dll' ?
perlis.dll is a permanent binding of the perl interpreter to the internal api of some w2k web-servers (for exampe the IIS). The advantage is to avoid loading the interpreter perl.exe for each page call. You may think of mod_perl for the apache, which binds the perl interpreter as some lib to the apache (and caches the the compiled perl scripts too, which perlis.dll does not). > Another thing - perl58.dll presumably gets loaded and perlis.dll > definitely gets loaded. So how come the 2 OpenSSL dll's could not get > loaded when they were in precisely the same directory ? Do you have tried to use perl.exe instead of perlis.dll? Dietmar _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
