Guys,
I think it is valuable to consider many different implementations of
session - even bad ones, so we get a good flexible session manager
implementation.
Remember that when we look at session persistance and session distribution
mechanism - lots of class loader issues will start cropping up. So even
if a EJB based persistent session proves to be horribly inefficient - it
would be a good test of the session classloading to share the classloader
of JBoss etc.
But when it comes to production quality session management - I don't think
we want to invent the whole wheel ourselves and we should build on
the work of others.
A few other things of note here - so we get the abstract model of a
session manager right - we should have a good look at other containers.
Gnu-paperclips for one is working towards pluggable session managers and
I have talked to them before about sharing session managers between
jetty and paperclips. So it would be good if we had a very very similar
API so we could just borrow (and donate) session managers. Thus it
would be worthwhile for folks to have a look at what they have done.
Secondly, the 2.3 servlet API has lots of session lefecycle and event
support in it. So when we abstract the session manager - we should
build in support for those lifecycles. Thus a quick read of the
2.3 servlet spec is in order.
I'm a little head down bum up at the moment to think about all this
in detail. What I plan is to concentrate on getting a 3.1.0 out
in the next week or two. Then immediately start a 3.2.A0 stream in
which we can break out the session manager and start playing with this
stuff.
cheers
--
Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462
Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631
http://www.mortbay.com AU Phone: +61-(0)2 98107029
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
