From: Mark W. <mor...@SM...> - 2002-12-21 01:58:53
|
Christian Bauer wrote: >On 20 Dec (17:37), Mark Woon wrote: > > > >>Have you considered using a filter to close the Session after everything >>is rendered? >> >> > >Yes, but closing/disconnecting the Session is _not_ the real problem. >The problem is: How and where does the Filter/Observer get and store the >Session to do its work? > > Ah. I'm storing it in the request attributes. If a page needs a Session, it checks to see if one already exists in the request attributes. If it doesn't, it creates one and sticks it into the request attributes. At the end, the filter checks to see if the Session exists, and if so, closes it. Isn't this a relatively simple way of doing it? -Mark |