Look there might be more than one way to skin this cat, I am of the opinion that the EJB solution, can be completely simple and transparent, the semantic that julian requested was a findbyprimary key that maps trivially to the ejb framework.
it is up to us to show that the container can be dedicated *using the distributed hastable* as the persistence (load and store would be get and set on the whole object, the object being the http session). I want to prove that EJB is a distributed SYSTEM construct, the moment we start seeing transactions accessing these stores (session) we would be able to include these trivially. So give me a chance to prove that point, something tells me that the EJB bashing is a by product of ignorance and strict spec interpretation. > That said, all you really need is a distributed > hashtable. There's already > one implemented as the Distributed State Service. No > coding, this is > already done. Can't get more simpler than that. > Implement an HttpSession > as a serializable object. "get" the session from the > DSS at the beginning > of an HTTP request, "put" the session back into the > DSS at the end of the > request. Simple as that. Well at least for the 1st > iteration :) slow down cowboy, you have been going fast these last days, you still need the finder semantic that Julian is asking for, not that it is complex but it stills needs to be there and it if you use EJB it is free and julian can work on it right now while we use the DSS to replicate the state with the code you have already written, the fancy invm cache we were talking about with Sacha can be your first iteration distributed hashtable. > 2. Also, sub-partitioning should really be handled at > the HAPartition level > and should be totally transparent to every other > clustering feature/service. > Configuring sub-partition sizes and whether > automatic-sub-partitioning > should be turned on or not should been done solely in > the HAPartition MBean. don't worry about this at first, the automatic topology partitioning is fancy but I don't foresee needing it immediately. > 3. I think the complexity starts to become a factor > when you start thinking > about concurrent access to HttpSessions. IMHO, it is > quite common to have 2 > different HTTP requests accessing the same HTTP > session concurrently. I > think you're going to need some sort of distributed > locking for HTTPSessions > otherwise people are going to come across some really > funky errors when they > start using this stuff. Of course, you don't need > distributed locking if > you require the load-balancer to give you "sticky" > sessions. Yes and this can be abstracted UNDER the EJB hood, marcf > Bill Bill, let this be, if I am wrong I will eat my words, but I something tells me this is what EJBs were really given to us for, heck I remember Vlada Matena pitching sessions and entity at the same level (user constructs) to SAP. i.e. not even these guys saw the system potential of the EJB construct, tweaking the persistence and putting a custom interceptor stack (no security says Julian...ok) would really prove the point in spades, I think, let me try it. 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
