Silly Question?

[Pjotr Wedersteers]

This may be a silly question, but I was wondering.

If 10 clients fill out a form on my page simultaneaously and hit submit, how
does my (Apache2.0.50/PHP4.3.8) server exactly ensure each gets 'their own'
completed form returned ? Or is it possible the clients get mixed up under
some conditions ?

TIA
Pjotr

[michel]

nope.... not possible.
apache tracks this, because it has a "dedicated line" to that specific user
(i.e. ip:port / socket)
don't worry 'bout it. it doesn't happen, unless someone effectively
interferes and spoofs that connection itself.

Michel

"Pjotr Wedersteers" <x3****@westerterp.com> wrote in message
news:41*********************@news.xs4all.nl...

This may be a silly question, but I was wondering.

If 10 clients fill out a form on my page simultaneaously and hit submit, how does my (Apache2.0.50/PHP4.3.8) server exactly ensure each gets 'their own' completed form returned ? Or is it possible the clients get mixed up under
some conditions ?

TIA
Pjotr

[Michael Austin]

Pjotr Wedersteers wrote:

This may be a silly question, but I was wondering.

If 10 clients fill out a form on my page simultaneaously and hit submit, how
does my (Apache2.0.50/PHP4.3.8) server exactly ensure each gets 'their own'
completed form returned ? Or is it possible the clients get mixed up under
some conditions ?

TIA
Pjotr

Apache may have several "server processes" that processes the data and each is
multi-threaded - meaning each server process can handle many simultaneous
connections. Each connection is seperate and cannot be mixed up. Considering
Apache is the number one server in production at sites that have hundereds of
hits per second, I don't think you have anything to worry about...

--
Michael Austin.

[Average_Joe]

In article <41*********************@news.xs4all.nl>, Pjotr Wedersteers wrote:

This may be a silly question, but I was wondering.

If 10 clients fill out a form on my page simultaneaously and hit submit, how
does my (Apache2.0.50/PHP4.3.8) server exactly ensure each gets 'their own'
completed form returned ? Or is it possible the clients get mixed up under
some conditions ?

Each request has a thread or more likely a process handling the request.
The thing that keeps them apart is the operating systems process model.

Sometimes things *can* get mixed up depending on the language and
design, but these are bugs more to do with programming the application
than PHP or Apache. (Servlets can sometimes have problems like this.)

Jamie
--
http://www.geniegate.com Custom web programming
User Management Solutions Perl / PHP / Java / UNIX

[Daniel Tryba]

Average_Joe <jo*@geniegate.com> wrote:

Sometimes things *can* get mixed up depending on the language and
design, but these are bugs more to do with programming the application
than PHP or Apache. (Servlets can sometimes have problems like this.)

The improvements with the PHP5 OO model should make it possible to use
these same Java/Servlet features in PHP :)

--

Daniel Tryba

[Average_Joe]

In article <cg**********@news.tue.nl>, Daniel Tryba wrote:

Average_Joe <jo*@geniegate.com> wrote:

Sometimes things *can* get mixed up depending on the language and
design, but these are bugs more to do with programming the application
than PHP or Apache. (Servlets can sometimes have problems like this.)

The improvements with the PHP5 OO model should make it possible to use
these same Java/Servlet features in PHP :)

I wish. :-( It's definately getting closer though!

Inner classes and objects that remain in memory after a request are the
main ones on my wish-list. (Also wish for a request type of
object where the parameters are not mangled as PHP does with it's $_POST
and $_GET arrays.)

'Course in a lot of ways, the way PHP does stuff seems to help keep away
some of the problems with servlets, like problems with thread
synchronizing and the startup sluggishness of JSP.

Jamie
--
http://www.geniegate.com Custom web programming
User Management Solutions Perl / PHP / Java / UNIX