<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">>Has someone already looked at techniques that involve the client asking for which documents (satisfying some criteria defined by the subscription) >have changed since the time the client last connected, and then as needed having the client ask for the latest version of some/all of those documents >(or parts of those documents)?</span><div>
<span style="font-family:arial,sans-serif;font-size:13px">Not that I'm aware of, at least I have not. </span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">The need for a client to ask for which document have changed did not really come up with the current demo using DS. The way this demo works is that there are multiple clients that edit a document identified with an documentId. The first client that connects adds the document, the following new clients will get the latest version that is on the server. For client that are reconnecting after being offline they will get patched with the edits to bring it up to date. Regarding how efficient this is that is probably is not :) The goals is mainly to try things out and see if would work out in real life.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 6 August 2014 16:47, Randall Hauch <span dir="ltr"><<a href="mailto:rhauch@redhat.com" target="_blank">rhauch@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 style="word-wrap:break-word"><br><div><div class=""><div>On Aug 6, 2014, at 1:27 AM, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>> wrote:</div><br></div>
<blockquote type="cite"><div class="gmail_extra"><div class="gmail_quote"><div class="">On 6 August 2014 00:34, Jay Balunas <span dir="ltr"><<a href="mailto:jbalunas@redhat.com" target="_blank">jbalunas@redhat.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div class="">
<div><div><div>I actually this this a very good point (as have other points on both sides). We will rely on people like you Randall to assist us in understanding the impact and advocate for the deeper server-side needs. While at the same time the client side APIs and developer experience will also need to be reviewed and taken into consideration.</div>
</div><div><br></div><div>I think it is important to remember that all of these are POC's and I think with a problem domain as complex as this, before we get to actual cross-project implementation we need to develop and flush out specs, including all of these various points, risks, etc... This would be across data services, liveoak and aerogear and possibly others.</div>
</div></div></div></blockquote></div></div></blockquote><blockquote type="cite"><div dir="ltr"><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class=""><div><span style="font-family:arial,sans-serif;font-size:13px">I think limiting the scope of this for now and enabling the underlying choice of storage/data service to be flexible will allow us to cater for the complex enterprise as well as a the simpler use cases which are important too if we want people to start using this and trying it out. </span></div>
</div></div></blockquote><br></div><div>Agree that the POCs should be focused and limited.</div><div><br></div><div>Has someone already looked at techniques that involve the client asking for which documents (satisfying some criteria defined by the subscription) have changed since the time the client last connected, and then as needed having the client ask for the latest version of some/all of those documents (or parts of those documents)? I know that’s not ideal from the client perspective, but this is extremely simple for the service to do. In fact, doing more than this in the service gets very expensive and very complicated very quickly.</div>
<div><br></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></div>