I have tested and tested and it seems to work just great! Keeping fingers crossed...
I'm just used to things not working so smoothly and with the warning on ATLCON I was wondering what I am missing, but so far, it runs a lot faster and works without a hitch. If you would like to take a look at the speed, e-mail me offline and I will send you a url. -bryanw -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 3:13 PM To: Bryan Waters; Discuss-List@Opensrs. Org; Dev-List@Opensrs. Org Subject: RE: PerlIIS The ISAPI filter used to be regarded by ActiveState as Beta Code but this does not seem to be the case anymore. It is meant to be much faster than the conventional implementation. I would be interested on anyone else experience with using the ISAPI filter. To configure this you need to go to the Application Mappings in IIS (Server Properties\Edit WWW Service\Home Directory\Configuration and associate .cgi with PerlIS.dll with the verbs GET,POST instead of perl.exe %s %s) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bryan Waters Sent: 24 October 2001 21:42 To: Discuss-List@Opensrs. Org; Dev-List@Opensrs. Org Subject: PerlIIS I just changed my Windows servers over to use PerlIIS and have tested the basic functionality and it seems to work. Everything I read says that the OpenSRS client scripts don't work under the PerlIIS dll. Can someone let me know which part doesn't work so I can test it? I am using the 2.4.1 client with Perl 5.6 from ActiveState... As I'm about to go live, I want to make sure I haven't broken something by this change... Can someone tell me which part is supposed to be broken under PerlIIS? -bryanw
