This is a discussion on newbie question - Apache vs IIS within the Apache Web Server forums, part of the Web Server and Related Forums category; "Crash" Dummy wrote... > The point of this autobiography is that there is no simple answer > to &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
"Crash" Dummy wrote...
> The point of this autobiography is that there is no simple answer > to "IIS or Apache?" Which to use depends on your circumstances. > If you just want to learn for some unspecified future application, > learn about both. If you are running XP Pro, I believe there is a > server included, although you will have to install it. First a alightly off-topic question to "Crash". Have you used ActiveX at all inside of PHP and Apache? Next, some answers for the OP. The NetScape browser was not very smart and I believe it ended up as an added expense which no one wanted to pay, and Microsoft added ActiveX (and a bunch of security problems) to Internet Explorer. It also came free with the operating system. So while there were / are some security issues with Internet Explorer (and all Microsoft OS's in general), there happens to be a lot of FREEDOM available. The freedom, meaning it's easy to do things (the Visual BASIC and ActiveX interfaces make it all a dream-come-true for programmers). So there's a lot of benefits for those using / doing work with IIS and Internet Explorer and VBA. Apache offers some advantages to IIS. There's PHP which is a true blessing for web-site programming and is easy to work with, much in the same way Visual BASIC is easy to work with. And there's Perl as well which offers an alternative, highly sophisticated scripting language which probably works a bit better than PHP but ends up as a tad bit more foreign, but once you learn the foreign characters used in Perl it ends up as a very powerful and beautiful language. There's a difference between Perl and other scripting languages as well. Perl gets compiled before it runs. Other scripting languages get loaded, and then parsed/run line-by-line. If there's a script error during the compile, I think Perl refuses to run the script and reports the error, so that perhaps provides an advantage over other scripting languages. If you set up IIS upon Windows XP, Microsoft broke XP, so that the number of connections limited to it (XP Pro, as IIS 5.1 does not come with XP Home) 10 concurrent connections. You'll need to get another TCPIP.SYS to get around that problem. TCPIP.SYS is the driver for TCPIP connections/networking and is found in %systemroot%\system32\drivers\tcpip.sys. There might be similar problems with other MS operating systems. Hope this information is helpful and useful. -- Jim Carlock North Carolina Swimming Pool Builders http://www.aquaticcreationsnc.com/ |
|
|||
|
> First a alightly off-topic question to "Crash".
> Have you used ActiveX at all inside of PHP and Apache? Nope. My web offerings are visited mostly by terminally paranoid security freaks. I can't even use client side scripts. Also, I didn't even know you *could* use ActiveX in PHP and Apache! I am pretty new to Apache. -- Crash Running: Windows 2000 Pro - IIS 5 - Apache 2.2.4 - PHP 5.2.1 - Perl 5.8.8 |
|
|||
|
Paul Pedersen wrote:
> My initial response would be "Apache of course, because it's by far the most > widely used". But I see from Netcraft > > http://survey.netcraft.com/Reports/200709/graphs.html > > that IIS usage has been growing rapidly, mostly at the expense of Apache. the netcraft web server survey is a census - it attempts to look at the Server header on every web(virtual)host on the internet, regardless of whether or not that website has any traffic. http://survey.netcraft.com/mechanics.html the netcraft survey gives as much credence to a desktop computer accidentally running a web service as it does to a domain-parking web server that has a million domains with zero daily traffic as it gives to a top-tier, high traffic server or server farm operating under a single hostname like cnn.com, myspace.com, wikipedia.org, google.com, cnet.com, or facebook.com, and fielding millions or billions of requests per day. imho it would be much more interesting to crawl the 100 or 1,000 most-trafficked web servers on the net and look at what's visible in _their_ Server: header: http://www.alexa.com/site/ds/top_sit...obal&lang=none here's a breakdown of Server: header among the alexa top-100 sites (some of these sites do not publish a Server: header, so the total is not 100) Server: count ======= ===== Apache 40 Microsoft-IIS 12 gws 21 nginx 3 AOLserver 2 GFE 2 lighttpd 2 Server 2 Resin 1 DMS 1 LiteSpeed 1 BWS 1 web 1 aris 1 TUX 1 --sean -- sean dreilinger - http://durak.org/sean/ |
|
|||
|
Paul Pedersen schrieb:
> If I were going to learn either Apache or IIS, which should it be, and why? > > > My initial response would be "Apache of course, because it's by far the most > widely used". But I see from Netcraft > > http://survey.netcraft.com/Reports/200709/graphs.html > > that IIS usage has been growing rapidly, mostly at the expense of Apache. > (And there's the sudden appearance of Google, which I know nothing about but > don't want to ignore.) I still remember what MS did to Netscape with IE. Is > that going to happen again? > > > What are the relative benefits and drawbacks of each? Apache has been made by real computer experts. IIS has been made by Microsoft's marketing division. -- Regards, Trinity Of Matrix E-Mail (only for spammer): trinity.matrix@localhost.localdomain |
|
|||
|
Interesting, thanks.
Any idea how those numbers have been changing over time? "sean dreilinger" <sean-usenet@durak.org> wrote in message news:13ehshp5eunabf8@corp.supernews.com... > Paul Pedersen wrote: >> My initial response would be "Apache of course, because it's by far the >> most >> widely used". But I see from Netcraft >> >> http://survey.netcraft.com/Reports/200709/graphs.html >> >> that IIS usage has been growing rapidly, mostly at the expense of Apache. > > the netcraft web server survey is a census - it attempts to look at the > Server > header on every web(virtual)host on the internet, regardless of whether or > not > that website has any traffic. http://survey.netcraft.com/mechanics.html > > the netcraft survey gives as much credence to a desktop computer > accidentally > running a web service as it does to a domain-parking web server that has a > million domains with zero daily traffic as it gives to a top-tier, high > traffic > server or server farm operating under a single hostname like cnn.com, > myspace.com, wikipedia.org, google.com, cnet.com, or facebook.com, and > fielding > millions or billions of requests per day. > > imho it would be much more interesting to crawl the 100 or 1,000 > most-trafficked > web servers on the net and look at what's visible in _their_ Server: > header: > > http://www.alexa.com/site/ds/top_sit...obal&lang=none > > here's a breakdown of Server: header among the alexa top-100 sites (some > of > these sites do not publish a Server: header, so the total is not 100) > > Server: count > ======= ===== > Apache 40 > Microsoft-IIS 12 > gws 21 > nginx 3 > AOLserver 2 > GFE 2 > lighttpd 2 > Server 2 > Resin 1 > DMS 1 > LiteSpeed 1 > BWS 1 > web 1 > aris 1 > TUX 1 > > --sean > > > -- > sean dreilinger - http://durak.org/sean/ |
|
|||
|
Paul Pedersen wrote:
> Interesting, thanks. > Any idea how those numbers have been changing over time? not continuously, but i did the same thing in july 2000: http://durak.org/sean/pubs/bss/ 2000 ======================== 38% - 48% apache, 22% - 27% microsoft IIS 18% - 25% netscape server and last week, among the alexa top-100 sites, we had: 2007 ======================== ~40% apache ~21% gws (google) ~12% microsoft IIS hth --sean > "sean dreilinger" <sean-usenet@durak.org> wrote in message >> imho it would be much more interesting to crawl the 100 or 1,000 >> most-trafficked >> web servers on the net and look at what's visible in _their_ Server: >> header: >> >> http://www.alexa.com/site/ds/top_sit...obal&lang=none >> >> here's a breakdown of Server: header among the alexa top-100 sites (some >> of >> these sites do not publish a Server: header, so the total is not 100) >> >> Server: count >> ======= ===== >> Apache 40 >> Microsoft-IIS 12 >> gws 21 >> nginx 3 >> AOLserver 2 >> GFE 2 >> lighttpd 2 >> Server 2 >> Resin 1 >> DMS 1 >> LiteSpeed 1 >> BWS 1 >> web 1 >> aris 1 >> TUX 1 -- sean dreilinger - http://durak.org/sean/ |