IIS Vs. Apache

Camper

New Member
Microsoft's IIS is gaining ground on Apache in the market share battle. According to a Netcraft survey Apache has a 50.48% market share and Microsoft has a 34.31% market share. In the last few months apache has been losing ground with Microsoft because of two newcomers Google and lighttpd. It possible that Microsoft might have the highest market share sometime in 2008.

Here is the Netcraft survey:
http://news.netcraft.com/archives/web_server_survey.html
 
yeah but how many of those registered domains are just parked for numbers? You have to realize that there are 1000s and 1000s of registered domains just parked somewhere. Hell, I own three domains and they are all parked because i haven't had time to build sites for them yet.

IIS, is crap. I have used it and supported it. It locks you into a proprietary format, unlike apache. Apache fully supports all standard and open source standards.
 
yeah but how many of those registered domains are just parked for numbers? You have to realize that there are 1000s and 1000s of registered domains just parked somewhere. Hell, I own three domains and they are all parked because i haven't had time to build sites for them yet.

IIS, is crap. I have used it and supported it. It locks you into a proprietary format, unlike apache. Apache fully supports all standard and open source standards.

Bad thing is this, Frontpage has become mainstream for basic website creation. You have to play around with your files from Frontpage to get them to work in Apache. IIS fully supports Frontpage...:rolleyes: No doubt, they are both absolute crap.

What does Apache actually support without having to mess around? And what type of files does Dreamweaver export for use?
 
What does Apache actually support without having to mess around? And what type of files does Dreamweaver export for use?

Perl, PHP, HTML, Java, CSS, CMS (content management systems), MySQL, python, ruby, basically any scripting language, oracle, web objects, and probably 100s more.

Dreamweaver is just really a gateway or translation application that translates your design to some sort of web based language, mainly HTML, but it supports a plethora of other languages.
 
Unless it's changed recently Dreamweaver makes html (sometimes with javascript but the webserver doesn't handle that) and css files. Every webserver supports those :P

I'd say the driving force behind IIS becoming more popular is .net not frontpage.
 
I'd say the driving force behind IIS becoming more popular is .net not frontpage.

Yup, and ASP.NET as well. I hate those technologies though. I also dislike MS SQL server, but that is because it is very picky about how you access it. In all honesty, this is actually where the open source market shines. Their products are actually better and more reliable, where as in every other case typically pay for software solutions tend to be better. You aren't going to run your Enterprise off open source products, with the exception of the web based solutions.
 
Perl, PHP, HTML, Java, CSS, CMS (content management systems), MySQL, python, ruby, basically any scripting language, oracle, web objects, and probably 100s more.

Dreamweaver is just really a gateway or translation application that translates your design to some sort of web based language, mainly HTML, but it supports a plethora of other languages.

Great, I am getting a Mac with Dreamweaver soon!! Does it regularly run good in Apache?

Yes, Noob here, I have to have WYSIWYG for this stuff..

Unless it's changed recently Dreamweaver makes html (sometimes with javascript but the webserver doesn't handle that) and css files. Every webserver supports those :P

I'd say the driving force behind IIS becoming more popular is .net not frontpage.

I didn't think about .net... Hmmm...
 
If you are getting a Mac, look into using NVU, it is just like dream weaver but free

http://nvudev.com/index.php

Apache is just the server, you can run it on your Mac if you want, and it is already installed by default. You just need to edit some files under /etc/httpd, or you need to get something like webmin installed and use it to configure your server. Then you point the server to all your files that make up your website. If coded properly it will all come up as intended.
 
If you are getting a Mac, look into using NVU, it is just like dream weaver but free

http://nvudev.com/index.php

Apache is just the server, you can run it on your Mac if you want, and it is already installed by default. You just need to edit some files under /etc/httpd, or you need to get something like webmin installed and use it to configure your server. Then you point the server to all your files that make up your website. If coded properly it will all come up as intended.

No the Mac is for me to Photoshop... I got that POS P4 and 965WH for this type of stuff... So using nVu I can just drop these folders into my Apache folder (httpd?) on my server and it's "Plug and Play"?


Thanx for link and help
 
I posted this up to alert the forum members about a passable change in the standard. There is enoff differences between the two that is the market swings to Microsoft then programs like Dreamweaver might change to integrate itself with IIS. It can also have an effect on other open source programs.
 
If memory servers, Apache's served directory is defaulted to /var/www/html

I think that is on windows, I was talking about *nix systems because of the mention of macs.

here are the base content of /etc/httpd/httpd.conf in OS X

Code:
ShopMacServer:/etc/httpd tlarkin$ cat /etc/httpd/httpd.conf
#### Default httpd.conf for Mac OS X Server
####
#### This httpd.conf differs from the httpd.conf distributed
#### with Apache and the httpd.conf present on Mac OS X.
#### Feel free to edit this; the Server Admin app also edits this file but will
#### respect your changes unless noted below. See also ReadMe.txt. 

##
## ServerType is either inetd, or standalone.  Inetd mode is only supported on
## Unix platforms.
##
ServerType standalone
##
## ServerRoot: The top of the directory tree under which the server's
## configuration, error, and log files are kept.
##
## NOTE!  If you intend to place this on an NFS (or otherwise network)
## mounted filesystem then please read the LockFile documentation
## (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
## you will save yourself a lot of trouble.
##
## Do NOT add a slash at the end of the directory path.
##
##
ServerRoot "/usr"
##
## PidFile: The file in which the server should record its process
## identification number when it starts.
##
PidFile /var/run/httpd.pid
##
## ScoreBoardFile: File used to store internal server process information.
## Not all architectures require this.  But if yours does (you'll know because
## this file will be  created when you run Apache) then you *must* ensure that
## no two invocations of Apache share the same scoreboard file.
##
ScoreBoardFile "/var/run/apache_runtime_status"
##
## Server-pool size regulation.  Rather than making you guess how many
## server processes you need, Apache dynamically adapts to the load it
## sees --- that is, it tries to maintain enough server processes to
## handle the current load, plus a few spare servers to handle transient
## load spikes (e.g., multiple simultaneous requests from a single
## Netscape browser).
##
## It does this by periodically checking how many servers are waiting
## for a request.  If there are fewer than MinSpareServers, it creates
## a new spare.  If there are more than MaxSpareServers, some of the
## spares die off.  The default values are probably OK for most sites.
##
MinSpareServers 1
MaxSpareServers 5
##
## Number of servers to start initially --- should be a reasonable ballpark
## figure.
##
StartServers 1
##
## MaxRequestsPerChild: the number of requests each child process is
## allowed to process before the child dies.  The child will exit so
## as to avoid problems after prolonged use when Apache (and maybe the
## libraries it uses) leak memory or other resources.  On most systems, this
## isn't really needed, but a few (such as Solaris) do have notable leaks
## in the libraries. For these platforms, set to something like 10000
## or so; a setting of 0 means unlimited.
##
## NOTE: This value does not include keepalive requests after the initial
##       request per connection. For example, if a child process handles
##       an initial request and 10 subsequent "keptalive" requests, it
##       would only count as 1 request towards this limit.
##
MaxRequestsPerChild 100000
##
## Dynamic Shared Object (DSO) Support
##
## To be able to use the functionality of a module which was built as a DSO you
## have to place corresponding `LoadModule' lines at this location so the
## directives contained in it are actually available _before_ they are used.
## Please read the file http://httpd.apache.org/docs/dso.html for more
## details about the DSO mechanism and run `httpd -l' for the list of already
## built-in (statically linked and thus always available) modules in your httpd
## binary.
##
## Note: The order in which modules are loaded is important.  Don't change
## the order below without expert advice.
##
## Example:
## LoadModule foo_module libexec/mod_foo.so
##
#### For Mac OS X Server: Note that the Server Admin application
#### and the apxs utility enable and disable modules
#### by removing and adding a comment character.

I didn't copy the whole thing. You can technically point Apache web server to any directory you want, but if you are publishing it to a web site host service, they will tell you want root directory to keep all your HTML stuff in.
 
I posted this up to alert the forum members about a passable change in the standard. There is enoff differences between the two that is the market swings to Microsoft then programs like Dreamweaver might change to integrate itself with IIS. It can also have an effect on other open source programs.

damn it always Micosoft.
I prefer apache thought cause of simplicity, never liked IIS due to all those configurations and stufd
 
I think that is on windows, I was talking about *nix systems because of the mention of macs.
That is *nix, not many windows systems have /var ;)

The windows root is program files\apache software foundation\apache<version>\htdocs
 
That is *nix, not many windows systems have /var ;)

The windows root is program files\apache software foundation\apache<version>\htdocs

Yeah but when you install other platform technologies on windows they tend to make their own directories.

But some distros do it different. /var typically holds log and some database files, at least in my experience
 
Last edited:
Back
Top