session - php page atomicity and consistency? -


Here is a potential scenario: A PHP page reaches a few session variables for session with SSID 1000. On the other tab, the user logs out, which means destroy the current session. I think the worst case scenario is: Code is still going on page 1. What happens in that situation? Code on page 1 still uses SSID 1000 from session wars, which no longer exists? Can I use the "catch hold" block to handle the possible exception? What happens to session session with SSID 1000, which I am using for DB queries on page 1?

I know that this question may be weird, but this scenario is important to me because I want to handle exceptions (if this situation raises an exception) and preventing DB from incompatible values. for.

In advance thanks

Web pages are stateless They "log in" or "log Out "are not in the state if the session is closing, when I see a page, efforts to continue using the session will fail. $ _SESSION will be rebuilt when I try to reach another page - a new session. Whatever you need as a web programmer, $ _SESSION is empty.

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -