Hello,
I would like to thank you guys very much for adding the built-in PHP web
server to PHP. For the first time I've just deployed a quick standalone app
without having to go through the trouble of configuring IIS or any other
web server. The installation was easy as ABC.
The built-in server was designed for development purposes and is not
suitable for production environments but IMO it's great for standalone
applications.
Keep up the good work and improve the features of the server when
necessary.
__
Raymond
Hello,
I would like to thank you guys very much for adding the built-in PHP web
server to PHP. For the first time I've just deployed a quick standalone app
without having to go through the trouble of configuring IIS or any other
web server. The installation was easy as ABC.The built-in server was designed for development purposes and is not
suitable for production environments but IMO it's great for standalone
applications.Keep up the good work and improve the features of the server when
necessary.__
Raymond
Even for standalone apps it's not a great idea to use it.
Hi William,
Why not?
On Wed, Dec 19, 2012 at 11:07 AM, William Betts william.betts@gmail.comwrote:
On Wed, Dec 19, 2012 at 10:05 AM, Raymond Irving xwisdom@gmail.com
wrote:Hello,
I would like to thank you guys very much for adding the built-in PHP web
server to PHP. For the first time I've just deployed a quick standalone
app
without having to go through the trouble of configuring IIS or any other
web server. The installation was easy as ABC.The built-in server was designed for development purposes and is not
suitable for production environments but IMO it's great for standalone
applications.Keep up the good work and improve the features of the server when
necessary.__
RaymondEven for standalone apps it's not a great idea to use it.
2012/12/19 Raymond Irving xwisdom@gmail.com:
Hi William,
Why not?
Thank you for the kind words Raymond (which should be addressed to
Moriyoshi Koizumi), but as mentioned on:
http://php.net/manual/en/features.commandline.webserver.php:
- It has never been created for anything else than development purpose only.
- It also cannot handle more than one request at a time, meaning that
if your application has several assets (images, js files, css
files,...) all of them will be downloaded sequentially. Situation that
is even worse if you have more than one concurrent user. - When it starts, it mentions: "Development Server started", please,
let me kindly emphasize the first word once more.
Criticisms have been raised about including that feature to the core
of PHP for the exact reason that it might be used as a simpler
alternative to real web servers. To avoid that, some stress has been
put on documentation to insist on not using it for anything else than
development.
There is also lot of programs bundling PHP, a web server and a
database server that are easy to use and configure.
Please, don't let room to bad practices which might end up damaging
PHP's reputation.
@Moriyoshi: Maybe you have more arguments to add?
Maybe we should list the reasons not to use it on anything else than
development on http://php.net/manual/en/features.commandline.webserver.php?
Regards,
Patrick
Hi Patrick,
Thanks for the feedback. I see your point and share some of your concerns.
> It also cannot handle more than one request at a time...
In my case a standalone web app will only be deployed on a single computer
and will only be used by one user at a time, so concurrency should not be a
problem. No other user will be able to access the application from the
network. These are basically single user web-desktop applications.
On Wed, Dec 19, 2012 at 12:33 PM, Patrick ALLAERT patrickallaert@php.netwrote:
2012/12/19 Raymond Irving xwisdom@gmail.com:
Hi William,
Why not?
Thank you for the kind words Raymond (which should be addressed to
Moriyoshi Koizumi), but as mentioned on:
http://php.net/manual/en/features.commandline.webserver.php:
- It has never been created for anything else than development purpose
only.- It also cannot handle more than one request at a time, meaning that
if your application has several assets (images, js files, css
files,...) all of them will be downloaded sequentially. Situation that
is even worse if you have more than one concurrent user.- When it starts, it mentions: "Development Server started", please,
let me kindly emphasize the first word once more.Criticisms have been raised about including that feature to the core
of PHP for the exact reason that it might be used as a simpler
alternative to real web servers. To avoid that, some stress has been
put on documentation to insist on not using it for anything else than
development.There is also lot of programs bundling PHP, a web server and a
database server that are easy to use and configure.
Please, don't let room to bad practices which might end up damaging
PHP's reputation.@Moriyoshi: Maybe you have more arguments to add?
Maybe we should list the reasons not to use it on anything else than
development on http://php.net/manual/en/features.commandline.webserver.php
?Regards,
Patrick