Search the Community
Showing results for tags 'destroy'.
Found 1 result
-
hello, I am writing an application that stores values in a session. At the end of the session, the session variables are stored in the db, there is some magic with these data and then a result is generated after which the session is destroyed. Everything is running as expected but for one thing. When the session is destroyed, I get to another page (eg by mistakingly clicking on something) and then want to go back to the result, the result gets destroyed as well. This is not what I want, I want the users to be able to keep the result (which is a page containing about 1000 words). I'd prefer not to store the complete result (again: 1000 words) in the database or in a new session, because when things are up and running there may be hundreds of users using the app simultaneously. I thought it would be possible to create a new session after the previous one is destroyed and setting the db id connected to the stored variables in a session variable so that the result could be recalculated every time the user gets back to the page. I am in doubt is this is the best way to handle this. What would be the best way to handle this situation?
