I've put aside some time early in January to try to get out my first cut.
It will be very simple, basically just de/re-hydrating HttpSessions on de/con-struction of the Jetty service. Initially my plan was to just use e.g. CMP to save the entire Session HashMap into the DB. I am now concerned that: 1). It is going to be difficult to ensure colocation (ClassLoader-wise) and therefore optimisation of distributed servlets and the HttpSession ejb-jar. 2). By using EJBs I may end up paying for functionality (speedwise) that I am not using... (authentication etc...). If this is the case, then would I be better off simply going native to the DB ? - would I not sacrifice portability ? This lies somewhere between dev and user lists, so apologies if you feel it should have gone to jboss-user. I considered cross-posting, but thought that might be even worse.... Thanks for your time, Jules distributed sessions upon destruction of a Jet __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
