Slashdot Mirror
IIS 7.0 Learns a Few Tricks from Apache
An anonymous reader writes "According to BetaNews, Microsoft is learning a few tricks from Apache for the next release of IIS, version 7.0. Specifically, the IIS feature set has been broken down into modules to reduce overhead. Modules can be changed on the fly, without restarting the Web server. Also, the IIS metabase has been completely dropped in favor of easily editable XML configuration files. Each Web application can have its own config file that overrides the system-wide configuration."
I link the XML configuration. Hopefully Apache does this soon. Editing the httpd.conf file is a real pain.
Bradley Holt
If Microsoft wants me to switch, they had better come out with something truly special rather than simply aping the rest of the industry.
I'd settle for a better IIS-FTP component, the one in IIS 6 is a bit of a joke. As for the Metabase , yes it could be more transparent but it isn't that complicated and there is an excellent programming interface for it. Most of all I'd really like to see Microsoft cough up the ability to configure absolutely every aspect of IIS (and Windows it self for that matter) from the commandline. Basically I want the option of being able to do absoloutely everything I can do with the Windows GUI admin tools but over a lousy GPRS connection via a remote text based shell. And this to the point where I don't have to see a Windows desktop for months should the need arise. Even in Windows 2003 the commandline toolkit that comes with Windows is incomplete although Microsoft does offer a bunch of administrator toolkits that help alot but I still fail to see why these have to be tracked down and downloaded seperately rather than being supplied with the OS.
Only to idiots, are orders laws.
-- Henning von Tresckow
I've been taking care of an Win2k3/IIS6 combo and to be honest, I've been quite happy with it.
"Research group Gartner is advising businesses to "immediately" replace their Microsoft Internet Information Server software with a more secure server application, following attacks on IIS by the worms Code Red and Nimda."
http://news.com.com/2102-1001_3-273461.html?tag=sGartner approves of Microsoft more often than not, and this was by far the most negative opinion I've ever seen them express about MS. Too bad hardly anyone took their advice.
Quantum mechanics: the dreams that stuff is made of.
Simply aping the rest of the industry has always worked for them before. Why change now? Because the other option is:
a) Free
b) Easily modifiable if you figure out something else you want it to do
c) More Stable
d) Running on an OS that's Free'er than yours
e) Kicking your tail
f) Preferred by Developers
g) All of the above
It might be mildly intelligent to actually add features that people really want badly to overcome the rest of the problems there....
My little site.
Excel? Nope, not purchased, 100% developed by Microsoft.
Now then, Powerpoint, Hotmail, Frontpage, etc were purchased.
But not Excel.
An application pool runs under an isolated process.
Multiple threads (configurable) service requests for this pool, in a pooled, as-available fashion.
So in the current system, you have visibility into the application pools, and you can see how many threads are servicing requests, there is no mechanism to make a given (hung or misbehaving) request visible and killable.
Now granted, this is a very minor feature, as if a typical asp or asp.net script is looping or hung, it'll either time out or be terminated by the system as a misbehaving execution.
So its nice, but the times when you need this granularity is rare.
In fact, the only times I've seen where it would be useful would be in killing runaway perl processes running under IIS. Currently, its difficult to figure out what script, or what request is looping/hung, and there is no automatic timeout for perl scripts or processes.