On the website, there are various different items that the user can configure. The data is stored in the session. If the user stops configuring the item before submitting it and starts configuring the new item, the configuration from the old item will still be stored in the session, right?
So I was wondering if I could get around this problem by having named sessions and destroying all sessions but the current one. How do I do this?
In other words, if the user is configuring item1 and the data is stored in the item1 session, and then the user stopped configuring item1 and started configuring item2, would I destroy the item1 session and starting the item2 session? Hope that is clearer. How do I do this programatically?