> running CFMX 6.1 to 2003/IIS6. The dlls for the web services
> extensions on the upgraded machine were different than the server
> where I installed CFMX 6.1 on a clean 2003/IIS6 install. The clean
> install had the dlls like jrun_iis6.dll under web services extension,
> whereas the upgraded machine had jrun.dll in the web services
> extensions.
>
> If CFMX 6.1 installed on a clean install of 2003/IIS6 does it install
> optimized dlls for IIS6? If so, does that mean that we should expect
> reduced performance with an upgraded machine that does not have the
> optimized dlls?
I haven't upgraded a machine from IIS 5 (W2K) to IIS 6 (W2K3), but I'm not
surprised that this happens. IIS 6 supports something called "IIS 5
compatibility mode", and I suspect that it's using this to run the CF ISAPI
DLL.
I doubt that you'll see much of a performance difference, really, but I'd
recommend that you remove and reinstall connectors if it's not too much
trouble. The IIS 6 connectors should offer some advantages in how they work.
In addition, they should be somewhat more secure; with IIS 5, CFMX typically
sets up an ISAPI filter in addition to an ISAPI extension, but with IIS 6,
CFMX uses a "wildcard" extension that's specific to IIS 6. This provides
some of the same functionality as a filter, but doesn't run as SYSTEM. So,
if it's compromised, the attacker won't be able to run code with such a high
privilege.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
