Ritu, I may totally misunderstand you, so please bear with me if I have got it completely wrong...
The users session is tied to the browser which initiates the connection. It is the same session however many windows that browser opens while connected to the Turbine application. Turbine is a single servlet which can handle many requests for different (usually but not necessarily *.vm) resources. So the single turbine application can result in many open windows for the same session/user. If you wish different windows opened by the same browser to share global data, then I believe that you can save that data in the user's session. If you need window specific data you need a method to identify the window and save a map of data keyed by the window id in the users session. You can then recover this window specific data by key and also have access to the session data. If you need different sessions ( opened by different browsers ) then you need a mechanism for holding application global data. As pointed out by Lester Ward, the GlobalCacheService does this and again you specify a key and save the data (or a map of data ) by key. This also has the benefit that orphaned data, which may happen if there is connection specific data and the browser loses its connection without properly logging out, can be timed out by the cache and expired and garbage collected in due course. Does this help? Regards, Peter On Wed, 2004-06-16 at 17:29, Goyal, Ritu (Ritu) wrote: > The "global sessions" are connected to specific users. I guess a better > way to say it would be that within a global session tied to one user, I > would like to initiate a separate local session that has access to > global data. All the classes provided by turbine seem to be tied to > users, and if that is the case, how would I separate my local and global > session data? > > Thanks, > Ritu.. > > -----Original Message----- > From: Lester Ward [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 16, 2004 9:45 AM > To: 'Turbine Users List' > Subject: RE: Maintaining separate session information in Turbine > > > What we really want to achieve is to be able to create > > session data that is global in scope for the main app, and > > session data that is local in scope for the wizards. > > You might be able to abuse the caching system to handle the global > sessions. > It sounds to me like what you are calling "global sessions" are really > just > collections of cached data anyway. I guess the difference would be: are > these "global sessions" connected to specific users? It didn't sound > like it > from your description. If they are not, than they are just global data, > which a cache can handle just fine. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
