"jpyorre" wrote : 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...
Congratulations!! Thanks for the time to come back to visit. :-) "jpyorre" wrote : 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). True. But this, IMO, has more impact on PojoCache (or TreeCacheAop). For TreeCache itself, the usage is always flat, per se. That is, user usually store the cache in a logical fashion without regarding much to the graph relationship. Case in point is you can store like year, month, week, day structure into the tree cache and it will fit nicely. "jpyorre" wrote : 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. Why do you need to maintain the tree-structure in the persistency store? Not that our solution now is fully optimized but we currently just store (fqn, node) (so to speak). No need of child parent relationship is needed. "jpyorre" wrote : 4. Graph-based cache would suits the Entity Bean replication quite perfectly. This is not quite true (I assume you talk about the entity cache). Currently, we use JBossCache behind Hibernate. So you see, Hibernate has taken care of the object relationship for us. TreeCache is again just a plain replicated cache system. I agree that PojoCache is well suit for this. But the reality of it is RDBMS is everwhere now. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927342#3927342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927342 ------------------------------------------------------- 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
