<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 12/09/2013 09:56 AM, Erik Jan de Wit
      wrote:<br>
    </div>
    <blockquote
      cite="mid:7C6E47FF-0BFB-4183-9A91-A6E3D18F520B@redhat.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>This proposal is just java based client API, if we nail down
        how a user could build an app that has sync functionality, all
        other things will fall into place. I suggest we keep the
        protocol and the server implementation as simple as possible and
        like qmx also suggested. JSON based with a hash as revision
        number for merging.<br>
      </div>
    </blockquote>
    <br>
    For real time sync this is a great primer:
    <a class="moz-txt-link-freetext" href="https://neil.fraser.name/writing/sync/">https://neil.fraser.name/writing/sync/</a>.&nbsp; The concepts can be
    expanded beyond text of course.<br>
    <br>
    I guess my question is do we want a really low level but universal
    protocol which requires server support, or several separate APIs
    which can handle legacy servers, servers with minor changes, or real
    time capable servers?<br>
    <br>
    As examples:<br>
    Legacy Servers can be periodic pollers.<br>
    Minor changes can be a sync on push type thing.<br>
    And realtime, is well, real time.<br>
    <br>
    <blockquote
      cite="mid:7C6E47FF-0BFB-4183-9A91-A6E3D18F520B@redhat.com"
      type="cite"><br>
      <div>
        <div>On 9 Dec,2013, at 14:30 , Sebastien Blanc &lt;<a
            moz-do-not-send="true" href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>&gt;
          wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <div dir="ltr"><br>
            <div class="gmail_extra"><br>
              <br>
              <div class="gmail_quote">On Mon, Dec 9, 2013 at 2:27 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 Mon 09 Dec 2013 02:44:59 AM EST,
                    Erik Jan de Wit wrote:<br>
                    &gt; My idea was that when the client calls sync the
                    server side state and the client side state get
                    merged and the delta is send<br>
                  </div>
                  So this would also require a server definition?<br>
                </blockquote>
                <div>I have the same interrogations, what do we want do
                  deliver :<br>
                  <br>
                </div>
                <div>- an Unified Synch Server ( USS )&nbsp; <br>
                </div>
                <div>- Client Libs (ios, android, web, cordova plugin)<br>
                  <br>
                </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">&gt;<br>
                      &gt; On 6 Dec,2013, at 18:16 , 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; One of the questions I have about this
                      API is how are push events handled with sync or is
                      this just an offline cache?<br>
                      &gt;&gt;<br>
                      &gt;&gt; IE how is data sent down to the client
                      when things change (or is that not for this use
                      case)<br>
                      &gt;&gt;<br>
                      &gt;<br>
                      <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>
            </div>
          </div>
          _______________________________________________<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 class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
      </div>
      <br>
      <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>