I've been away from work for a while (on honeymoon) and a lot seems to have happened since I last time visited the the forum...
"[EMAIL PROTECTED]" wrote : No, AFAIK we're not thinking about moving away from a TreeCache-based approach, or at least if we are it's way back in the back of someone's mind. But can we get the benefit of your experiences anyway? :) We're definitely interested. I was asking about this graph-based POJO cache just because I see so many benefits in a graph-based cache compared to tree-based cache (here are just a few): 1. It always causes problems when forcing a less restricted structure in a more restricted structure, as the case is when forcing a graph structure into a tree structure (tree is a special case of a graph). I'm sure that you are more than aware of this problem... The other way (forcing a tree into a graph) there are no such problems. 2. Implementing two things at the same time (caching and tree-structure) creates very complex and bug-inducing code because you have to handle all kinds of special cases of tree-structure and caching simultaneously. If tree cache was build on top of graph cache (instead of the other way) the code would be more modular and at least a magnitude shorter (this is just an educated guess). 3. Persistence of a tree-structure is relative slow as you have to maintain the tree structure in the database i.e. tree node is dependent of all its parent nodes. Graph has no such dependencies (references to a certain node are direct by using a unique identifier for each node, instead of using a recursive path of nodes as an identifier) and thus is much faster. However, if using graph-based cache as the basis of a tree cache, the performance of persistence would still be equal to the current implementation. 4. Graph-based cache would suits the Entity Bean replication quite perfectly. "ScottMarlowNovell" wrote : I compared the performance of this new implementation against what I checked in on December 5th 2005 and don't see much difference: | ... I'm not surprised as your implementation (on December 5th) seems very similar to mine. I wasn't aware that you have already made improvements (these changes were not yet in 1.2 release and I haven't accessed JBossCache version control), my bad. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926523#3926523 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926523 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
