> I guess what I"m really saying is that you have to be
> careful if you're
> implementing the HttpSession in terms of EJBs.

ok sure

1- we can configure a custom stack of interceptors the overhead of security and 
transactions is nill (virtually) but we could remove it.  
2- what is really expensive is serialization, RPC and database
a- go with local stacks where we don't serialize, we use the clustering to set it up 
and recommend load balancers that can configure sticky session
b- we go with real distributed state, no configuration needed
c- we write a trivial CMP engine, in fact we don't write we plug in your distributed 
DSS thingy from the clustering UNDER the CMP store API and voila we have an entity 
semantic to find the stuff with your hashtable under the covers

If this performs well, we will have proven one of the biggest points of EJB in JBoss.  
All it takes is putting that DSS in a CMP API wrapper.

Works like a dream.

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

Reply via email to