Current PHP implementation

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

I ask this question in 'comp.unix.programmer. It seems like it is more  
related to PHP.

I ask here to find out the current PHP implementation.

Assume at a given time 10 users send in AJAX calls; server end handled by  

1. Handler (script): 123.php

Does the server initiate 10 processes to handle the calls ? Which means 10  
processes are closed after processing !?

2. Handler (daemon): 123.php

Is the daemon/server creating 10 threads to handle requests ? Which means  
the daemon is always running. Please ignore the memory problem of PHP.

Thanks for any info. Happy Boxing day.

Using Opera's revolutionary email client: /

Re: Current PHP implementation

On 12/25/2012 8:51 PM, SL@maxis wrote:
Quoted text here. Click to load it

PHP doesn't handle AJAX calls, nor does PHP start any processes.  That
is all done by the web server.   You need to be asking in a newsgroup
for the webserver you are using.

Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.

Re: Current PHP implementation

On Tue, 25 Dec 2012 21:45:58 -0500, Jerry Stuckle wrote:

Quoted text here. Click to load it

If the client calls a php script using the client side ajax mechanism,
then the php script handles the ajax call.

However, what part of the client generates the call is irrelevant to the
php. All that the php script "knows" is that it has been invoked in an
environment that may include several predefined arrays. It has no idea
whether it was invoked from a link click, a form submission, an embedded
object or an ajax call, although it may be able to determine this from
its data environment.

Denis McMahon,

Re: Current PHP implementation

Peter H. Coffin wrote:

Quoted text here. Click to load it

And unsurprisingly, what you posted is not even close to being correct, the
PHP part included.
Quoted text here. Click to load it

No, typically (read: apache-mpm-prefork on a Linux-based system) there will
be two server processes that have 10 threads each, which will continue to
run until the server is shut down.

In any case, with PHP run by server module or FastCGI, the parent process
will like *never* exit as long as the server system is running uninterrupted
(i.e., without reboot and maintenance).

Started threads will likely exist until the Web server service is stopped.  
New child processes will be created if the number of threads in a child
process exceed the specified maximum.  Threads in a child process will be
created so as to meet the specified minimum and number of spare threads.

Quoted text here. Click to load it


So you figured.  But you posted this utter nonsense anyway?  You have way
too much time on your hands.

Quoted text here. Click to load it

There is nothing to be gained from reading a “w3sc***ls page” and much to be
lost.  Most of all, clarity of thought and overall mental sanity.  Of which
your posting is a good example.

Quoted text here. Click to load it

Me too.

When all you know is jQuery, every problem looks $(olvable).

Re: Current PHP implementation

Quoted text here. Click to load it



Leder efter redundant peering af dk.*,linux.debian.*

Re: Current PHP implementation

Anders Wegge Keller wrote:

Quoted text here. Click to load it

Indeed, that is another constraint I overlooked.  However, if I am not
mistaken, both the default value and default distribution configuration file
value¹ is 0, which means that those two child processes will never expire,
and AIUI neither will their threads.


¹  I was checking my /etc/apache2/apache2.conf.dpkg-old, mtime 2009-12-04.
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
  -- from < (404-comp.)

Re: Current PHP implementation

SL@maxis wrote:

Quoted text here. Click to load it

It is not more related to PHP as apples are to oranges.

Quoted text here. Click to load it

Do you know what PHP is?

Quoted text here. Click to load it

|    AJAX call \noun\
|        Term indicating that the per-
|        son using it has no clue what
|        they are talking about.  See
|        also: AJAX.

Quoted text here. Click to load it

Server processes are not the domain of the compiler-interpreter of a
programming language, but of the Web server software.

Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.

Site Timeline