> I've put aside some time early in January to try to > get out my first cut.
excellent > Initially my plan was to just use e.g. CMP to save > the > entire Session HashMap into the DB. yes, I argue that using the implementation that is in there with the SFSB in memory could be a big time saver, but that is besides the point just use CMP and we will plug in the right persistence. > 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. Don't worry about this, a- I am working as we speak on the integration of the classloaders that won't be a problem b- the clustering of SFSB detects colocation in the proxy already so that is taken care of for you. > 2). By using EJBs I may end up paying for > functionality (speedwise) that I am not using... > (authentication etc...). This functionality 1- you pay nothing 2- we remove it with the JBoss container (we don't configure the security stack). The optimization of the that is really something that is independent of you. Just go ahead. > If this is the case, then would I be better off > simply > going native to the DB ? - would I not sacrifice > portability ? no no no, use that EJB and we will plug in persistence that can stay in VM... that is EJB for you :) marcf ______________________________________________________________________ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66&thread=6221 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
