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

Getting PHP to work under IIS wasn't any big deal if I remember correctly. Follow any instructions you can find for installing it under IIS 5, and then take the extra step in IIS 6 to add PHP as a valid server extension. Read through this page, then check out the user comments at the bottom. http://www.php.net/manual/en/install.iis.php John ----- Original Message ----- From: "Harpreet" <harpreet@crispincorp.com> To: "JPoz" <jpoz@quickscribble.com>; <php-windows@lists.php.net> Sent: Monday, April 21, 2003 9:15 AM Subject: Re: [PHP-WIN] Re: APACHE server on a machine that already has IIS = > We have more then 100 customers who already run have window NT machines and > IIS and right now have ASP web apps. We cannot change them to APache servers > and would like a way to confgure the IIS to understand PHP. > > The slowness wont effect us as the app is preety small. > > How can I get IIS to understand PHP. Is ther a web site that explains it. Is > it a simple process. Please help. > > Thanks, > > Regards, > Harpreet > ----- Original Message ----- > From: "JPoz" <jpoz@quickscribble.com> > To: "Cory Daehn" <cdaehn@pobox.com>; <php-windows@lists.php.net> > Sent: Saturday, April 19, 2003 4:44 PM > Subject: Re: [PHP-WIN] 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. > > > > > > > > > > -- > > PHP Windows Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > >