<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:48 AM, Matthias
      Wessendorf wrote:<br>
    </div>
    <blockquote
cite="mid:CAAg5f2RNoYEGu7DsS9d6nednihERbpH7qj5MC0hhAAtwfu_nNg@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:54 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 10:48 AM, Lucas Holmquist
                wrote:<br>
                &gt; On Jan 28, 2014, at 10:30 AM, Summers Pittman &lt;<a
                  moz-do-not-send="true"
                  href="mailto:supittma@redhat.com">supittma@redhat.com</a>&gt;
                wrote:<br>
                &gt;<br>
                &gt;&gt; On 01/28/2014 09:36 AM, Lucas Holmquist wrote:<br>
                &gt;&gt;&gt; yup, this is another Data Sync thread,<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; &nbsp;From a client side perspective, i have
                concerns that there is still not a clear direction yet.<br>
                &gt;&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;&gt; All the data model is is an envelope of sync
                metadata around an object<br>
                &gt;&gt; right?<br>
                &gt; right<br>
                &gt;<br>
                &gt;&gt; We also need to think about the API and
                server/client protocol as well.<br>
                &gt;&gt;<br>
                &gt;&gt; I think that for sync 1.0 we could focus on the
                following behavior (it<br>
                &gt;&gt; worked for my demos at least)<br>
                &gt;&gt;<br>
                &gt;&gt; 1. &nbsp;We have a Sync factory similar to Pipeline,
                Authenticator,<br>
                &gt;&gt; Registrar, and KeyService.<br>
                &gt;&gt; 2. &nbsp;The Sync factory consumes/manages
                Synchronizer instances.<br>
                &gt;&gt; 3. &nbsp;AG Synchronizer listens for sync messages
                using UnifiedPush endpoints.<br>
                &gt; i thought for a 1.0 we weren't thinking about
                "realtime"<br>
              </div>
              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. &nbsp;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>
            </blockquote>
            <div><br>
            </div>
            <div>You mean using Mobile Push to send actual content?
              &nbsp;Hrm, I guess that does not work w/ SimplePush;</div>
          </div>
        </div>
      </div>
    </blockquote>
    No not really.&nbsp; I mean what I said in the other email when you asked
    the same question ;)<br>
    <blockquote
cite="mid:CAAg5f2RNoYEGu7DsS9d6nednihERbpH7qj5MC0hhAAtwfu_nNg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>The mobile push is really more for notification that
              "something" has changed. Clients than could ping the
              sync-server for latest value</div>
          </div>
        </div>
      </div>
    </blockquote>
    Yes.&nbsp; This ^^.&nbsp; That is what my "ideal" will do for 1.0<br>
    <blockquote
cite="mid:CAAg5f2RNoYEGu7DsS9d6nednihERbpH7qj5MC0hhAAtwfu_nNg@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">
              <div class="HOEnZb">
                <div class="h5"><br>
                  &gt;<br>
                  &gt;&gt; 4. &nbsp;AG Synchronizer sends sync messages using
                  Pipes<br>
                  &gt;&gt; 5. &nbsp;AG Synchronizer holds local data in a
                  store<br>
                  &gt;&gt;<br>
                  &gt;&gt; 6. &nbsp;When AGSynchronizer gets a message it is
                  responsible for updating<br>
                  &gt;&gt; the Store and then notifying code listing for
                  updates OR for notifying<br>
                  &gt;&gt; the code that an error has occurred and needs
                  to be addressed.<br>
                  &gt;&gt;<br>
                  &gt;&gt; 7. &nbsp;When the developer updates data in the
                  store, the synchronizer<br>
                  &gt;&gt; should package that data and send it to the
                  server. &nbsp;The synchronizer is<br>
                  &gt;&gt; responsible for error handling, retrying,
                  back-off, etc.<br>
                  &gt;&gt;<br>
                  &gt;&gt; 8. &nbsp;We should include multiple synchronizer
                  implementations to deal with<br>
                  &gt;&gt; multiple very simple use cases which involve
                  legacy systems. (For<br>
                  &gt;&gt; instance polling to load static data on a
                  schedule.)<br>
                  &gt;&gt;<br>
                  &gt;&gt; Thoughts? Tomatoes?<br>
                  &gt;&gt;&gt;<br>
                  &gt;&gt;&gt;<br>
                  &gt;&gt;&gt;
                  _______________________________________________<br>
                  &gt;&gt;&gt; aerogear-dev mailing list<br>
                  &gt;&gt;&gt; <a moz-do-not-send="true"
                    href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
                  &gt;&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;&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>
                  _______________________________________________<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>