At 01:50 PM 1/10/02 -0500, [EMAIL PROTECTED] wrote: >I thought that the ISAPI leak was fixed? > >I cannot remember.
I don't think so. There were some fixes to wkcgi.exe recently, but I don't remember seeing anything related to ISAPI. >Looking at the code, the application IP and port # seem to be hard coded >into the .dll > >The wkcgi.exe uses an external file, but the dll seems to want to find the >application on localhost at port 8086. > >I need it to open a socket to the application server on 192.168.2.40 > >The speed w/ wkcgi is too slow, mainly due to the firewall. They are >dedicated to IIS and already have the SSL certificate installed so I >cannot easily change to Apache. Why would the firewall slow down wkcgi.exe any more than the ISAPI filter does? As far as the socket connections are concerned, I think they pretty much do the same thing -- establish a new socket connection for each request. CGI is generally somewhat slower on Windows due to Windows' high process spawning overhead. -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
