That doesn't look too difficult. Thanks... I'll think of something as to
prevent the 2nd page from showing up in the 2nd browser window or 2nd
browser tab window or with the back/forward browser button..
Scott
Jason Barnett [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
--
PHP
Scott Fletcher wrote:
I created the token via Javascript where the billing can be controlled
better and to prevent the mixed up of the billing such as incorrect
statements or calculation. I use the billing lock file for that purpose. I
found that it doesn't alway work that way when the browser
I can do the Session Token but problem is two browser windows can have the
same Session Token via File -- New Window or Browser Tab. I have thought
about using the Database Table instead but it all go back to the original
problem with 2 same browser windows that use the same Session.
I'm
Scott Fletcher wrote:
I can do the Session Token but problem is two browser windows can have the
same Session Token via File -- New Window or Browser Tab. I have thought
about using the Database Table instead but it all go back to the original
problem with 2 same browser windows that use the same
Never heard of the uniqid() before and looked it up on the php.net. It look
very promising. I can do that. That leave me with 2 questions. How do I
do (or how does it work) this with a token if
1) The webpage is submitted (goes from page 1 to page 2) with the uniqid().
2) The 2nd browser
Scott Fletcher wrote:
Never heard of the uniqid() before and looked it up on the php.net. It look
very promising. I can do that. That leave me with 2 questions. How do I
do (or how does it work) this with a token if
1) The webpage is submitted (goes from page 1 to page 2) with the uniqid().
2)
6 matches
Mail list logo
