<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 28, 2014 at 6:08 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 bgcolor="#FFFFFF" text="#000000"><div class="im">
<div>On 01/28/2014 11:46 AM, Matthias
Wessendorf wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Jan 28, 2014 at 4:48 PM,
Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@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><br>
On Jan 28, 2014, at 10:30 AM, Summers Pittman <<a href="mailto:supittma@redhat.com" target="_blank">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>
>><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>
<br>
</div>
right<br>
<div><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>
</div>
i thought for a 1.0 we weren't thinking about "realtime"<br>
</blockquote>
<div><br>
</div>
<div>that is my impression as well, talking to Dan on IRC;</div>
<div>ATM all is polling, but the sync-server will be cable
of doing WebSocket/SockJS, so "connected" clients, can
sync.</div>
</div>
</div>
</div>
</blockquote></div>
Polling is MURDER on battery, performance, and "feel". WebSockets
and SockJS are awesome ideas for a future implementation for "real
time".</div></blockquote><div><br></div><div>As far as I understood it, the sync-server just started w/ polling (pure HTTP). I think that WebSocket/SockJS is not really that far away, in terms of 'future'</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div class="im"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Push should be really used for 'wake-up', instead of
changing real information; Also SimplePush clients could
not even integrate here (the protocol just uses version
(or timestamps)</div>
</div>
</div>
</div>
</blockquote></div>
Yes.<br>
<br>
On the topic of Simple Push, you push a URL so in theory you could
push /Documents/${collecitonName}/${id}/${rev_id} and have simple
push setup to accept URLS formatted that way right? Or is it more
limited than that?</div></blockquote><div><br></div><div>you can simply ONLY push a version number, that's it</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div><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>
>><br>
>><br>
>>
_______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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" target="_blank">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>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div></div></div>
<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></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>