Re: [PHP] Re: PHP as Application Server

2012-09-27 Thread Maciej Liżewski
to Matijn Woudt: you are right there should be something like: public void synchronized increment(), but that is not the point. Sure there are disadvantages and other problems but what Alessando is saying is I would not use cure for cancer even if it existed because it can introduce other problems

[PHP] Re: PHP as Application Server

2012-09-27 Thread Alessandro Pellizzari
Il Thu, 27 Sep 2012 12:28:00 +0200, Maciej Liżewski ha scritto: Sure there are disadvantages and other problems but what Alessando is saying is I would not use cure for cancer even if it existed because it can introduce other problems like overpopulation. Uhm, no. I see it as I would not

Re: [PHP] Re: PHP as Application Server

2012-09-27 Thread Sebastian Krebs
Hi, Once again I didn't read it completely (maybe I will do so), but my 2ct: I recently played with Ruby and Python and of course with their application server (at least a little bit). My experience was, that it is less fun as it sounds in the first place compared to a well designed

[PHP] Re: PHP as Application Server

2012-09-26 Thread Jim Giner
On 9/26/2012 5:58 AM, Maciej Liżewski wrote: Hi, Maybe this topic have been already on board, but I could not find nothing in google, so my question to PHP maintaneers (and other users too) is: Why there is no possibility to run PHP in application server way among other SAPI modules and other

Re: [PHP] Re: PHP as Application Server

2012-09-26 Thread Maciej Liżewski
Well.. many things changed during last 30 years. Cobol is not mainstream, we have got OOP, Java, Python, Ruby, Google and other great things :) I am talking about stateful application server. There are plenty examples in other programming languages: Java has Jetty, Tomcat, Ruby On Rails, Python

[PHP] Re: PHP as Application Server

2012-09-26 Thread Alessandro Pellizzari
Il Wed, 26 Sep 2012 17:23:35 +0200, Maciej Liżewski ha scritto: persistent application servers load resources only on startup (or when needed) and keep them in memory until programatically freed or until end of application (server shutdown). You don't mention the downsides: - every

Re: [PHP] Re: PHP as Application Server

2012-09-26 Thread Jim Giner
On 9/26/2012 11:23 AM, Maciej Liżewski wrote: Well.. many things changed during last 30 years. Cobol is not mainstream, we have got OOP, Java, Python, Ruby, Google and other great things :) I am talking about stateful application server. There are plenty examples in other programming languages:

Re: [PHP] Re: PHP as Application Server

2012-09-26 Thread Matijn Woudt
On Wed, Sep 26, 2012 at 5:23 PM, Maciej Liżewski maciej.lizew...@gmail.com wrote: in Java (for example) you just write class: class Counter { static private counter = 0; public void increment() { this.counter++; } } And here's where things go wrong.. You assume ++ is an atomic

Re: [PHP] Re: PHP as Application Server

2012-09-26 Thread Robert Williams
On 9/26/12 10:18, Matijn Woudt tijn...@gmail.com wrote: Writing scripts for an application server requires a much deeper understanding of threads and computer internals,so as a result it probably increases error rate. Well... yes and no. PHP's architecture pretty much keeps you from having to