anonymous wrote : | | This is an excellent proposal. Especially, branching off Cache from Node which was totally confusing! I would suggest to consider moving some methods from Cache to CacheSPI, like TransactionalManager and InvocationContext if possible. If you read carefully your post you already have this planned I believe. | | Some things, yes, but not all. Remember that typical end-user apps will not have access to the CacheSPI, just the Cache. Which includes things like Brian's http session repl code and Hibernate's TreeCacheProvider. Both of these would need access to the InvocationContext to set specific options. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994632#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...