<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 28, 2014 at 6:14 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 01/28/2014 11:41 AM, Lucas Holmquist wrote:<br>
> On Jan 28, 2014, at 11:01 AM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
><br>
>> On 01/28/2014 10:58 AM, Lucas Holmquist wrote:<br>
>>> On Jan 28, 2014, at 10:54 AM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
>>><br>
>>>> On 01/28/2014 10:48 AM, Lucas Holmquist wrote:<br>
>>>>> On Jan 28, 2014, at 10:30 AM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
>>>>><br>
>>>>>> On 01/28/2014 09:36 AM, Lucas Holmquist wrote:<br>
>>>>>>> yup, this is another Data Sync thread,<br>
>>>>>>><br>
>>>>>>>> From a client side perspective, i have concerns that there is still not a clear direction yet.<br>
>>>>>>> I know there are multiple ideas floating around on what our model should be, i'm all for choice, but what about deciding on 1 model to get started with. Then later once we have this nailed down, we can have other "adapters" with different models perhaps<br>
>>>>>> All the data model is is an envelope of sync metadata around an object<br>
>>>>>> right?<br>
>>>>> right<br>
>>>>><br>
>>>>>> We also need to think about the API and server/client protocol as well.<br>
>>>>>><br>
>>>>>> I think that for sync 1.0 we could focus on the following behavior (it<br>
>>>>>> worked for my demos at least)<br>
>>>>>><br>
>>>>>> 1. We have a Sync factory similar to Pipeline, Authenticator,<br>
>>>>>> Registrar, and KeyService.<br>
>>>>>> 2. The Sync factory consumes/manages Synchronizer instances.<br>
>>>>>> 3. AG Synchronizer listens for sync messages using UnifiedPush endpoints.<br>
>>>>> i thought for a 1.0 we weren't thinking about "realtime"<br>
>>>> When I hear realtime I think sub 100 ms updates to all clients. (think<br>
>>>> gaming)<br>
>>>><br>
>>>> What I thought we were going for was something closer to email. The<br>
>>>> data gets changed and at some point in the future the client knows. More<br>
>>>> specifically, the thing the ONE thing that makes sync special is it is a<br>
>>>> push instead of poll implementation.<br>
>>> this makes sense, but i guess it would be push when available. thinking web and crappy web socket support( dang you carriers )<br>
>> Right. I'm not saying lets do something complicated. I'm saying lets<br>
>> use GCM, iOS CM, and simple push to send notifications to tell the<br>
>> client something. In simplePush case it is "this data changed, get the<br>
>> new stuff and update yourself". In Android and iOS case it may be that<br>
>> or it may be "here is new data".<br>
>><br>
>> In general, I am fine for getting a message saying something like<br>
>> Documents/Schedules/1/${revision}. Then I can check my revisions, fetch<br>
>> data if necessary, update my local data, and send any updates. That<br>
>> SHOULD (I think) be doable with simplepush as well right?<br>
><br>
> not sure how i feel about using "push"( APNS, GCM, SimplePush ) stuff for sync.<br>
> then we are relying on these 3rd party services,<br>
</div></div>That is a valid concern.<br>
<br>
I think making our entire sync product based on polling is a bad thing.<br>
(Battery, performance, etc etc etc).<br>
I think making sync based on TCP sockets/WebSockets/SockJS is a good<br>
thing, but it is past 1.0<br></blockquote><div><br></div><div>regarding 1.0 - I am not even sure what that version should be done; but for me (personal thought),</div><div>I (again, personally) have serious doubts that the first sync offerings (March/April?) will be the ones labeled as '1.0.0';</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think making our sync product demand proprietary technology is a bad<br>
thing, but I don't know of a service which is as easy as APNS or GCM for<br>
iOS and Android devs.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
><br>
>>>>>> 4. AG Synchronizer sends sync messages using Pipes<br>
>>>>>> 5. AG Synchronizer holds local data in a store<br>
>>>>>><br>
>>>>>> 6. When AGSynchronizer gets a message it is responsible for updating<br>
>>>>>> the Store and then notifying code listing for updates OR for notifying<br>
>>>>>> the code that an error has occurred and needs to be addressed.<br>
>>>>>><br>
>>>>>> 7. When the developer updates data in the store, the synchronizer<br>
>>>>>> should package that data and send it to the server. The synchronizer is<br>
>>>>>> responsible for error handling, retrying, back-off, etc.<br>
>>>>>><br>
>>>>>> 8. We should include multiple synchronizer implementations to deal with<br>
>>>>>> multiple very simple use cases which involve legacy systems. (For<br>
>>>>>> instance polling to load static data on a schedule.)<br>
>>>>>><br>
>>>>>> Thoughts? Tomatoes?<br>
>>>>>>> _______________________________________________<br>
>>>>>>> aerogear-dev mailing list<br>
>>>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>>>>> _______________________________________________<br>
>>>>>> aerogear-dev mailing list<br>
>>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>>>> _______________________________________________<br>
>>>>> aerogear-dev mailing list<br>
>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>>> _______________________________________________<br>
>>>> aerogear-dev mailing list<br>
>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>> _______________________________________________<br>
>>> aerogear-dev mailing list<br>
>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>