Re: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method?

2009-06-09 Thread Keith
Craige, Marc, Nitsan,Bastien, Thanks for your reply! This is my understanding and comment from your replies: (1) If the web server do have assign anonymous request ID to each HTTP request from client browser, and assign $_POST to each request ID and works within request ID scope, this is fine w

RE: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method?

2009-06-09 Thread HallMarc Websites
-Original Message- From: Craige Leeder [mailto:clee...@gmail.com] Sent: Tuesday, June 09, 2009 11:54 AM To: Keith; PHP-General List Subject: Re: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method? While yes $_POST is a supergloabal, even a

Re: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method?

2009-06-09 Thread Craige Leeder
While yes $_POST is a supergloabal, even a superglobal has it's own scope. The scope of $_POST is to the call of the user to the web server. Therefor, no User A's information will not be overwritten by User B's information. Hope this helps. Let me know if you want any further clarification. Th

Re: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method?

2009-06-09 Thread Bastien Koert
On Tue, Jun 9, 2009 at 11:51 AM, Nitsan Bin-Nun wrote: > Hell no! > > Why would they be overwritten? > > An HTTP request is sent from user A, the interpreter is "compiling" > the PHP script with the received HTTP request variables and send back > the HTTP response to user A, during this time the sa

Re: [PHP] Any conflict with $_POST when 2 users concurrently submitting the same form using POST method?

2009-06-09 Thread Nitsan Bin-Nun
Hell no! Why would they be overwritten? An HTTP request is sent from user A, the interpreter is "compiling" the PHP script with the received HTTP request variables and send back the HTTP response to user A, during this time the same thing happens with user B. I can't think of any possible reason