On Sat, Jun 4, 2011 at 6:28 AM, Luciano Resende <[email protected]>wrote:
> On Fri, Jun 3, 2011 at 4:48 PM, Umashanthi Pavalanathan > <[email protected]> wrote: > > Hi devs, > > I am in the process of adding persistence support to the social API using > > JCR. > > For that first we have to decide on the node structure. I have come up > with > > two options (please refer attached image). > > In option-1, for each username, we have profile,activity,appdata,messages > > child nodes. > > In option-2, under nodes people,activity,appdata,messages, we have child > > node for each user. > > Referring to the two options, which is more suitable in your opinion? > > > > Thanks, > > ~Umashanthi > > I think if we have a good understanding of the data access pattern, it > can help us decide which structure to use. For example, if we would > mostly show list of activities by user, and all other data by user, > I'd go with option 1. > Yes; as I understood we would mostly access data by user and my +1 for the option-1. Thanks, ~Umashanthi > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
