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."

5 of 395 comments (clear)

  1. Erm by Vlad_Drak · · Score: 5, Informative

    IIS 6.0 utilized an editable-during-runtime xml configuration file, metabase.xml. The new stuff is more integrated into a .Net Framework style config.

  2. Saw a demo of it a few weeks ago.. by Johnno74 · · Score: 4, Informative

    ... At TechEd New Zealand. IIS7 looks really smart, with pluggable modules to provide all of its functionality, as the submitted mentioned. Ouf of the box pretty much everything will be disabled, and you enable only the modules you need.

    IIS6 (win 2003) has already done away with the metabase and gone to an XML file for all of the configuration settings.

    IIS7 goes one further, by allowing you to put configuration files in each virtual directory or website to over-ride the parent setting (if permitted) - this allows a website owner to configure their own website, without affecting the other websites on the box, or having to ask the administrator to make the changes for them.

    The MS guy told me they are trying to make management as easy as possible for servers containing thousands of seperate sites. He also said they hope to release IIS7 for Win2003 R2.

    Loads of other management things are coming in too, such as the ability to examine currently execting requests, and kill them without restarting the site or server (VERY usefull if a script is looping)

    MS's new approach to security seems to be really paying off - IIS6 was re-written from the ground up, and how many security holes have there been? I can't remember any.

  3. Re:Not XML by Rasta+Prefect · · Score: 3, Informative

    Running in prefork MPM is fine for the most part, but I really wish perchild would get off the ground so that PHP scripts won't be all running as the same user. Now if only all of PHP's modules were thread safe...

    suPHP will take care of that for you. Well, the user bit, not the thread safety bit.

    http://www.suphp.org/Home.html

    --
    Why?
  4. Re:so... by SomeGuyTyping · · Score: 3, Informative

    that's what Mono is for

    --
    My posts are definitive. Reality is frequently inaccurate.
  5. Re:XML Config by Anonymous+Crowhead · · Score: 3, Informative

    Would have been nice had he done one of these first:

        mv /etc/httpd/conf/httpd.conf /etc/httpd/conf/httpd.conf.bak


    Heh, fat chance with that guy. I usually append a bind type serial number (2005091501) to the end of a copy. If you just use .bak you can accidently write a bad copy over a good one. Even worse is finding things like:

    httpd.orig.bak3 or
    httpd.conf.this.one.works2.bak

    in the conf directory.