The guy is right - he needs IIS. If he is going to code MS-based ASP pages, he will need an ASP engine (whether IIS or Chili!Soft ASP) that supports the MS-based syntax. The same goes for ActiveX - natively it will need IIS. There are some workarounds (such as remote execution with a Java to COM bridge), but sticking with IIS is the best solution. As for the custom DLLs, it really depends on what those DLLs are going to be. If they are to be ISAPI modules, then any server supporting 100% ISAPI compatible should be able to run those same modules (unless they tie into other IIS-specific functions). And concerning XML, there are more options than just IIS.
So, overall, if this guy wants all this in one server, IIS will be his best bet. However, some of the headache he saves in trying alternative servers will come back to haunt him in the area of security. He will need to be ever-vigilant for bugs and their patches.
-Jeff
-----Original Message-----
From: Rodney Richison [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 10:49 PM
To: [EMAIL PROTECTED]
Subject: [sambar] why IIS? {01}
A guy on another forum said he needed a Win2k server with IIS. I was geniunely curious as to why. Here's the answer I got. Any comments?
***********************************
ASP, XML, custom dll's and activeX controls that I make with VB, etc..
***********************************
Highest Regards,
Rodney Richison
------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
