Re: Re: APACHE server on a machine that already has IIS =

Yeah, I've seen the Apache/FP plug-in, but I don't know Apache that well. I have it running, got virtual namedservers going, password protected directories, etc. I know IIS far better than I know Apache. But instead of dealing with this Apache/FP add-on, it was just easier to leave IIS for this one client. (I also use IIS' FTP server for my webmasters to upload with.) Perhaps I'll look into this add-on at a later date. My reason for switching to Apache was because of the terrible way IIS handled PHP. It was so slow, a simple database query with about 30 returns (7 field per return) took more than 60 seconds to "draw" the HTML in a while loop. With Apache, it's nearly instananeous. I don't know if this is IIS or the PHPxx.DLL for IIS. Either way, I'm now happily running Apache 1.3.27 on Windows 2000 Advanced Server and Windows 2003 RC2 (formerly .Net) Web Edition Server. John ----- Original Message ----- From: "Cory Daehn" <cdaehn@pobox.com> To: "'John'" <jpoz@quickscribble.com>; <php-windows@lists.php.net> Sent: Saturday, April 19, 2003 4:59 AM Subject: RE: [PHP-WIN] Re: APACHE server on a machine that already has IIS = Actually, John, you're not. You can install FrontPage extensions on an Apache server. Of course, nobody bothers to mention to the guy that you can install PHP as a module of IIS. But why would anyone want to keep a sorry web server software like IIS? I can't count how many times I go to IIS servers and get a 503 - Server Too Busy error message.... there's even an ASP module for Apache. :) But again, why would anyone want to use such a poorly written language as ASP? It's about 300% slower than PHP. > Sure. Like the other guy said, make sure they listen on > seperate ports. > Actually, I still am forced to use IIS because one of the > companies I hosts > insists on using FrontPage. I let him connect to IIS, via FP, > on port 9999 > and let Apache dish out the normal web pages on port 80.