<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/29/2014 03:08 AM, Matthias
      Wessendorf wrote:<br>
    </div>
    <blockquote
cite="mid:CAAg5f2TxN4KFOfgjJLxSExp2imFy4765p=+cJ9O=-brLvSRdTQ@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 7:24 PM,
            Douglas Campos <span dir="ltr">&lt;<a
                moz-do-not-send="true" href="mailto:qmx@qmx.me"
                target="_blank">qmx@qmx.me</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="HOEnZb">
                <div class="h5">On Tue, Jan 28, 2014 at 10:30:47AM
                  -0500, Summers Pittman wrote:<br>
                  &gt; On 01/28/2014 09:36 AM, Lucas Holmquist wrote:<br>
                  &gt; &gt; yup, this is another Data Sync thread,<br>
                  &gt; &gt;<br>
                  &gt; &gt; &gt;From a client side perspective, i have
                  concerns that there is still not a clear direction
                  yet.<br>
                  &gt; &gt;<br>
                  &gt; &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>
                  &gt; All the data model is is an envelope of sync
                  metadata around an object<br>
                  &gt; right?<br>
                  &gt;<br>
                  &gt; We also need to think about the API and
                  server/client protocol as well.<br>
                  &gt;<br>
                  &gt; I think that for sync 1.0 we could focus on the
                  following behavior (it<br>
                  &gt; worked for my demos at least)<br>
                  &gt;<br>
                  &gt; 1. &nbsp;We have a Sync factory similar to Pipeline,
                  Authenticator,<br>
                  &gt; Registrar, and KeyService.<br>
                  &gt; 2. &nbsp;The Sync factory consumes/manages
                  Synchronizer instances.<br>
                  &gt; 3. &nbsp;AG Synchronizer listens for sync messages
                  using UnifiedPush endpoints.<br>
                  &gt; 4. &nbsp;AG Synchronizer sends sync messages using
                  Pipes<br>
                  &gt; 5. &nbsp;AG Synchronizer holds local data in a store<br>
                  &gt;<br>
                  &gt; 6. &nbsp;When AGSynchronizer gets a message it is
                  responsible for updating<br>
                  &gt; the Store and then notifying code listing for
                  updates OR for notifying<br>
                  &gt; the code that an error has occurred and needs to
                  be addressed.<br>
                  &gt;<br>
                  &gt; 7. &nbsp;When the developer updates data in the store,
                  the synchronizer<br>
                  &gt; should package that data and send it to the
                  server. &nbsp;The synchronizer is<br>
                  &gt; responsible for error handling, retrying,
                  back-off, etc.<br>
                  &gt;<br>
                  &gt; 8. &nbsp;We should include multiple synchronizer
                  implementations to deal with<br>
                  &gt; multiple very simple use cases which involve
                  legacy systems. (For<br>
                  &gt; instance polling to load static data on a
                  schedule.)<br>
                  <br>
                </div>
              </div>
              The thing I have against all this is its curse and its
              blessing at the<br>
              same time. I prefer to ship small-ish tools that the
              developer can use<br>
              the way she wants instead of a full-blown-zomg-unicorns
              full-stack<br>
              solution.<br>
              <br>
              Even the pipeline API requires some level of buy-in, and I
              really wish<br>
              our DataSync API to be as decoupled as possible from the
              other parts.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I agree on the decoupling. That's pretty much what the
              iOS lib does today: Only dependency is AFNetworking;</div>
            <div>The JS bits are similar, nothing is weaved into the
              existing APIs there as well</div>
            <div><br>
            </div>
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              This was my main concern when I was saying: "focus on the
              datamodel<br>
              first, then the update protocol, then...."<br>
            </blockquote>
            <div><br>
            </div>
            <div>I think we somewhat agreed already on a document based
              model, now it looks like several POCs are build to
              integrate w/ our sync-server bits</div>
          </div>
        </div>
      </div>
    </blockquote>
    Just out of curiosity, what other models are there? [Also I think it
    will be better to say metadata + object model instead of document.&nbsp;
    Document is 1) very generic and 2) has very different definitions
    depending on what we are thinking]<br>
    <blockquote
cite="mid:CAAg5f2TxN4KFOfgjJLxSExp2imFy4765p=+cJ9O=-brLvSRdTQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              If we start with a fully integrated solution, it will be
              awesome, if we<br>
              have buy-in from the developer. And we all know that
              things not<br>
              necessarily go this way with OSS projects, hence my
              kerfuffle against<br>
              increasing sync's scope for 1.0.<br>
            </blockquote>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>So, what will the scope be? And will there be a 1.0 ? <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    ^^ This.&nbsp; One of the things we have been failing at doing (and
    failing hard) is defining a scope for sync.<br>
    <blockquote
cite="mid:CAAg5f2TxN4KFOfgjJLxSExp2imFy4765p=+cJ9O=-brLvSRdTQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>I am not really sure that we will have a 1.0.0 in the
              next few month.</div>
            <div><br>
            </div>
            <div>-Matthias</div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              What's the MVP for the sync to be a good foundation for
              all the shiny<br>
              bits? That's the question I want to have a good answer
              for.<br>
              <div class="im HOEnZb"><br>
                &gt;<br>
                &gt; Thoughts? Tomatoes?<br>
                &gt; &gt;<br>
                &gt; &gt;<br>
                &gt; &gt;<br>
                &gt; &gt;
                _______________________________________________<br>
                &gt; &gt; aerogear-dev mailing list<br>
                &gt; &gt; <a moz-do-not-send="true"
                  href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
                &gt; &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>
                &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>
              </div>
              <span class="HOEnZb"><font color="#888888">--<br>
                  qmx<br>
                </font></span>
              <div class="HOEnZb">
                <div class="h5">_______________________________________________<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>