I have developed an extensive app, working with a single user during the development. I am now getting close to launching this as a public multi-user webapp.
I just discovered (thanks to Tim Hare) that properties in a module of a webapp are accessible across multiple sessions of that webapp. What this means to me is that in a multi-user environment, information I need to keep private to a session (for information privacy as well as preventing one session from stepping on the toes of another session) needs to leverage properties that are part of a session as opposed to part of a module.
From a coding perspective, that looks to me like I need to address all of my session properties as “session.propertyname”. Adding “session.” to all my properties that need app-wide access is a bit cumbersome. Is there a more efficient way to address session.properties without the “session.” prefix? Or are there other strategies for accomplishing what I have described above?