<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 01/28/2014 11:44 AM, Matthias
      Wessendorf wrote:<br>
    </div>
    <blockquote
cite="mid:CAAg5f2TWf1gbhU=qnDcXoBOdv3JHOREHD3MFhVZEqOsSXu_1rQ@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Tue, Jan 28, 2014 at 4:30 PM,
            Summers Pittman <span dir="ltr">&lt;<a
                moz-do-not-send="true" href="mailto:supittma@redhat.com"
                target="_blank">supittma@redhat.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im">On 01/28/2014 09:36 AM, Lucas Holmquist
                wrote:<br>
                &gt; yup, this is another Data Sync thread,<br>
                &gt;<br>
                &gt; &gt;From a client side perspective, i have concerns
                that there is still not a clear direction yet.<br>
                &gt;<br>
                &gt; I know there are multiple ideas floating around on
                what our model should be, &nbsp;i'm all for choice, but what
                about deciding on 1 model to get started with. &nbsp;Then
                later once we have this nailed down, &nbsp;we can have other
                "adapters" with different models perhaps<br>
              </div>
              All the data model is is an envelope of sync metadata
              around an object<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. &nbsp;We have a Sync factory similar to Pipeline,
              Authenticator,<br>
              Registrar, and KeyService.<br>
              2. &nbsp;The Sync factory consumes/manages Synchronizer
              instances.<br>
              3. &nbsp;AG Synchronizer listens for sync messages using
              UnifiedPush endpoints.<br>
            </blockquote>
            <div><br>
            </div>
            <div>W/ "sync message" you mean something like a 'heads-up'
              from the server it has something new, instead of the
              concrete delta/diff ?&nbsp;</div>
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              4. &nbsp;AG Synchronizer sends sync messages using Pipes<br>
            </blockquote>
            <div><br>
            </div>
            <div>Like: "server, my local copy changed!" ?</div>
          </div>
        </div>
      </div>
    </blockquote>
    Or, more specifically, "Here is new data"<br>
    <blockquote
cite="mid:CAAg5f2TWf1gbhU=qnDcXoBOdv3JHOREHD3MFhVZEqOsSXu_1rQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              5. &nbsp;AG Synchronizer holds local data in a store<br>
              <br>
              6. &nbsp;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. &nbsp;When the developer updates data in the store, the
              synchronizer<br>
              should package that data and send it to the server. &nbsp;The
              synchronizer is<br>
              responsible for error handling, retrying, back-off, etc.<br>
              <br>
              8. &nbsp;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>
              <div class="HOEnZb">
                <div class="h5">&gt;<br>
                  &gt;<br>
                  &gt;<br>
                  &gt; _______________________________________________<br>
                  &gt; aerogear-dev mailing list<br>
                  &gt; <a moz-do-not-send="true"
                    href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
                  &gt; <a moz-do-not-send="true"
                    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 moz-do-not-send="true"
                    href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
                  <a moz-do-not-send="true"
                    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 moz-do-not-send="true"
            href="http://matthiaswessendorf.wordpress.com/"
            target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
          sessions: <a moz-do-not-send="true"
            href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
          twitter: <a moz-do-not-send="true"
            href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>