Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Just throw it in a database. You're bending over backwards to accommodate limitations of the session. Commented Jul 9, 2010 at 19:55
  • The database would have the same issue unless I apply a workaround. Since it's two different applications in the DB, it would have 2 separate sessions. Commented Jul 9, 2010 at 21:38
  • You misunderstand my suggestion. Instead of using the session at all,place whatever persistent data you require in a common database. Sessions, and cookies, are engineered to keep applications from stepping on each other, which requires isolation. This is one of the many things that databases are good for. Commented Jul 10, 2010 at 5:59