In my opinion, IIS/Windows takes less time to configure PHP with than both Apache/Windows and Apache/Linux. Apache/Windows takes more time to configure because you're pretty much adapting Windows to a Linux-based technology and it's not just as simple as whipping through a bunch of tabs and clicking OK. Apache/Linux takes more time to configure (for the Windows user) because: 1. you have to learn the tricks and commands of your Linux distro before you can even start and 2. you are sometimes required to use the command line in great detail. By great detail, I mean that you have to type a lot more than you would if you were using IIS. If you're not a keyboard jockey, and you've gotten used to the way Windows operates, you're at the mercy of those keys. Now, with that said, I can put these three configurations side-by-side on the same hardware, and load a fairly complex page from it, and for the most part the Apache/Linux web server will always deliver the page faster, although not by much. Your minutes spent learning the ins and outs of Linux pay off in many many seconds less of load time for the end user. So my favorite configuration is Apache/Linux, namely Apache/Fedora. It is also worth noting that one can save a massive amount of time by using 'yum' in Fedora to install Apache and PHP. You can also use yum to install mysql. I would also note that I am far less familiar with Apache and Linux than I am with IIS and Windows, and yet I prefer the former for a web server. As far as actual features of each... both seem to work properly with PHP5. I haven't had any major issues with either one yet, but then again, I don't usually program anything too hard core with PHP. Also, most options that are in IIS seem to be available in Apache, save one. This is Windows Active Directory authentication. I would assume it could be done in Apache using LDAP (or something else) to access Active Directory, but it would require a learning experience. I would rather just use IIS if I had to integrate AD into the web site security simply to get the job done faster. There is also the issue of ASP code. If you have any currently running from a Windows/IIS server, it is a pain to move to Apache and get ASP working. I have yet to do it with Apache:ASP simply because I JUST DON'T GET IT, but I am fairly sure that if I just paid for Sun's Java ASP, I could get it done. -Aaron Kenney On 5/23/06, giorger <giorger@xxxxxxxxx> wrote:
Thanx for the info. It seems as if u have worked with both IIS and apache. What are the advantages and the disadvantages and in general what would u recommend. Aaron Kenney wrote: > The indication that I get from the documentation is that PHP 5 isn't > compatible with Apache versions higher than 2.0.58, at least in > Windows. Eventually I am sure that the PHP people will get this > working. It just takes some time to do a release. > > I have PHP 5 running on IIS on a Windows 2003 server, but I also have > PHP 5 running on Apache 2.2.0 on a Fedora Core 5 server. So I know > that PHP5/Apache 2.2.x does work on Fedora Linux when installed > through yum. If you have the capability, perhaps you'd like to go that > route if you must use this combination. > > Otherwise, I can try installing this combination on my Windows XP Pro > test PC at the next possible moment. > -Aaron Kenney > > On 5/23/06, giwrgos <giorger@xxxxxxxxx> wrote: >> Hi! >> I tried to install Apache 2.2 and PHP-5.1.4 as a module but i failed. >> The reason is that apache cannot load the php5apache2.dll. The file >> exists. So, i was wondering if PHP isn't supporting apache2.2. If there >> is any help, that would be great! >> Btw,i am using WinXP Pro. >> >> -- >> PHP Windows Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
