From: <bst...@jb...> - 2006-06-23 18:36:20
|
To clarify a bit more on the requirements re: FIELD http session repl: Ben, you mentioned somewhere that we shouldn't support cross-webapp shared references. Actually, with BR, even cross-session shared references will not work. Say a POJO was an attribute in two different sessions. Then the data owner fails, and the load balancer assigns the two sessions to 2 different AS instances. From now on those two AS instances will fight over the shared POJO gravitating it from one to the other as requests come in!!! So, if people want shared objects across sessions, they can't use BR. Given that, *for the http session repl use case* I don't need the get() to go through the interceptor stack on a getObject() call. When JBossCacheManager calls get() on the root of the session, all attributes will be gravitated. What I do need for http session repl is for any call that accesses a node under /_JBossInternal_/_RefMap_ to go through the interceptor stack. That is, just the call from InternalDelegate.getRefFqnFromAlias(). How many such calls would there be for a given child node under _RefMap_ during a putObject()? From a brief look at the code I don't see how there would be many. You would need at least one to go through the interceptor stack in order to lock the _RefMap_ child node. (Actually, looking at it now I'm not sure any call to a _RefMap_ child node would go through the interceptor stack, and thus you don't get a RL on that node, which seems wrong). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953100#3953100 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953100 |