Re: [infinispan-dev] Tree API module wiki
Great, finally an easy migration from JBoss Cache.
Just to know our options in Mobicents future, are there any cons on
using this API? Is there a reason to change a data model/schema coming
from JBoss Cache, that really takes advantage of node relations
parent/child? For instance it's very common to retrieve the set of
childs for a node, another common usage is the removal for a complete
subtree. We have time to rework this data model if it's not the best
usage, we want it as fast as possible, both local and cluster/cloud
modes.
-- Eduardo
..............................................
http://emmartins.blogspot.com
http://redhat.com/solutions/telco
On Thu, Nov 11, 2010 at 11:53 AM, Manik Surtani <manik(a)jboss.org> wrote:
Nicely done!
On 10 Nov 2010, at 16:53, Galder Zamarreño wrote:
> I've just finished writing http://community.jboss.org/docs/DOC-16081
>
> Anything that should change? Anything extra that should be included?
>
> Scott, I believe you've played quite a bit with the tree module, so it'd be
great to hear your feedback as a user :). Maybe we should add a section to explain when it
makes sense to use the tree module API, i.e. to build a JNDI repo?
>
> Cheers,
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev