Re: PHP4/Win

Hi All, Al lot of work is beeing done on the Windows platform. But there still is a lot of work to do. PHP3 was written for Apache where each request started a new process. In order to get performence on NT IIS uses threads. Threads are quick to launch but they share memory. Therefore PHP and all the modules needs to be thread safe in order to work with the ISAPI version of PHP4. Personally I think PHP is the number one development language for Web applications. I have been using it for three years on Windows (and Linux) and our company has more that 250 satified customers using PHP3 on Windows NT as the backend for Intranet applications. It would be nice to see PHP used instead of ASP on Windows installations. Switching from ASP to PHP is the first step in the right direction. Next step could be the switch from IIS to Apache and then from Windows to Linux depending on the needs. - Frank >Daniel Gustafsson wrote: > >> At 11:12 2000-10-06 -0400, you wrote: >> >I agree. What do you suggest we do? >> >> Form a mob? > >Now that's a great idea ;) > >> I'm not doubting the current efforts or anything, but a little >> feedback and encouragement never hurts =) >> >> Having a stable Apache module (and stable version of apache itself) for >> windows wouldn't hurt either. I've found some interesting material up at >> www.php4win.de anyhow. > >Just chiming in with my 2 cents... I used to (and still am in some ways) a >big fan of IIS... it's graphical management capabilities are great - for the >non-command-line techie (can you be one?) IIS is nice to manage and >pretty-darn-powerful. > >That being said, I was *forced* to switch over to Apache a few months ago (my >new workstation at my new job didn't have ANY web server running, and I >figured "what the heck.") And I must say, in that time, I've been VERY >impressed with 1) Apache Win32s performance, 2) its flexibility, and 3) how >well it matches the workings of the Unix environment. Most everything I do >locally is for hosting on Unix web & application servers, so working in as >much of a Unix-like environment is very helpful. So, I guess I encourage >anyone who has the inkling to try out Apache (heck, just install it on a >different port on your current web-server, and see what you get... for all >the "warnings" about Apache Win32 being "unstable" - I have yet to see >problems. Of course, this is just a development workstation and not a >production webserver. But there ARE people out there hosting websites on >WinNT with Apache. > >And I agree that flexibility is best... if you want or must use IIS, then php >should take care of you, as well as those running Apache or OmniHTTP or >whatever popular webserver you'd like to use. Guess I'd kind of expect the >apache code to be "safer" however, as MANY of the Unix php gurus also run >Apache as their webserver of choice. > >Know what I mean? > >-- >Andy Hoffman >Web Developer >Bristol-Myers Squibb >email: andy.hoffman@bms.com > > >-- >PHP Windows Mailing List (http://www.php.net/) >To unsubscribe, e-mail: php-windows-unsubscribe@lists.php.net >For additional commands, e-mail: php-windows-help@lists.php.net >To contact the list administrators, e-mail: php-list-admin@lists.php.net > > >