[aerogear-dev] DataSync or SyncPipe API proposal

Summers Pittman supittma at redhat.com
Mon Feb 10 10:26:51 EST 2014


On 02/10/2014 10:24 AM, Lucas Holmquist wrote:
> On Feb 10, 2014, at 9:48 AM, Summers Pittman <supittma at redhat.com> wrote:
>
>> On 02/10/2014 08:46 AM, Lucas Holmquist wrote:
>>> On Feb 10, 2014, at 8:44 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>
>>>> So iOS and JS are at the same level of API fucntionalities and same method names.
>>>> we’re just left to pick a name DataSync vs SyncPipe
>>> yea,  i wasn't really thrilled with DataSync when i named it that
>> Because it isn't Sync.  It is VersionControl
> exactly,  Then perhaps we should be calling this first set of Milestones, Version Control client API instead of Data Sync
+1

>
>
>>>> Let’s see for the Java version
>>>>
>>>> ++
>>>> Corinne
>>>> On 10 Feb 2014, at 14:40, Lucas Holmquist <lholmqui at redhat.com> wrote:
>>>>
>>>>> On Feb 10, 2014, at 6:38 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>>>
>>>>>> Hello Guys,
>>>>>>
>>>>>> Following discussion on ML thread [1], and JIRA discussion [2] (sorry guys I catched up the discussion late, I wasn’t watching the JIRa ticket so i didn’t get notifications) here is the 2 gists we have:
>>>>>> 1. DataSync (JS naming) [3]
>>>>>> 2. SyncPipe(ios naming) [4]
>>>>>>
>>>>>> I guess we should call them the same and agree on a name. I like to use ‘pipe’ in the naming just to recall it’s async and going through network. I found DataSync a too generic term which may lead to confusion. This is not the same object that will save data offline and trigger sync.
>>>>>>
>>>>>> Main differences are: in iOS one I defined a readAll method. Also for save/update I define a third callbacks ‘conflict’ which take 3 arguments .
>>>>> in JS the read method can also be "read all",  should probably update that gist
>>>>>
>>>>>> @summers do you have a gist for java API?
>>>>>> thoughts?
>>>>>>
>>>>>> ++
>>>>>> Corinne
>>>>>> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-sync-To-pipe-or-not-to-pipe-td6135.html
>>>>>> [2] https://issues.jboss.org/browse/AEROGEAR-1408
>>>>>> [3] https://gist.github.com/lholmquist/81de9737b5c91367aa3c
>>>>>> [4] https://gist.github.com/corinnekrych/8914290
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



More information about the aerogear-dev mailing list