[aerogear-dev] Sync data model comparison

[Lucas Holmquist]

after playing with dan's server a bit,  a question has popped up.  

lets say a user has 10 pieces of data,  is this considered 1 "document", so like this:

{
    id: "1234567890-0987654321-1234567890",
    rev: "12345678909876543456787654",
    content: [ { ... }, { ... } ] //make believe there are 10 things there
}

or is each piece of data a "document", and each piece has its own id and revision?

I think i like the first option, but i'm not sure


On Jan 9, 2014, at 11:07 AM, Summers Pittman <supittma at redhat.com> wrote:

> On Thu 09 Jan 2014 11:06:26 AM EST, Bruno Oliveira wrote:
>> Makes sense, I think that’s a great start is to integrate your idea against what Dan already did to the server, into this way we can start to put together our puzzle.
> 
> Yup, just got Danbev's server up and running.  I'll see what happens :)
> 
>> 
>> --
>> abstractj
>> 
>> On January 9, 2014 at 12:37:19 PM, Summers Pittman (supittma at redhat.com) wrote:
>>>> One of the things about using a provider that I don't like is the
>>> "using a provider". One of the things I hope sync to become is a
>>> collection of tools, utilities, and patterns that our developers
>>> can
>>> adopt to add in sync to their web apps without having to add extra
>>> services like couch, pouch, etc and without having to significantly
>>> alter their application.
>>> 
>>> HOWEVER, I am still reading up on / playing with Couch so don't
>>> count
>>> me out on thinking it is a good way to go forward; I just havn't seen
>>> any code to get the feel for how it will interact inside of AeroGear.
>>> It is entirely possible that it will be / can be one of the tools
>>> that
>>> we use for some of our sync solution.
>> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev