<div dir="ltr">><span style="font-size:12.8000001907349px">One thing that this brings up that I didn't see in the AGSYNC Jira </span><span style="font-size:12.8000001907349px">(unless I'm blind) was how to manage the socket-connectivity interaction </span><span style="font-size:12.8000001907349px">on the >clients. </span><div><span style="font-size:12.8000001907349px">You are right there is no JIRAs for this and it would be great if you could create one (We should have one for iOS as well). Could this be a targeted for an alpha.2 release?</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 February 2015 at 05:14, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
First the good news, I've refactored a lot of the xmpp-client code so<br>
now the sync client is correctly handled by an Android service. This<br>
gets around issues we were having earlier where the in-memory client<br>
would get GCed while the doc was in the background as well as some<br>
issues with loading documents when messages came in for the not<br>
currently being edited doc.<br>
<br>
Now the bad news, the past two weeks we've been focusing on using<br>
Google's two way messaging for being the backbone of sync on Android for<br>
alpha.1. One of the issues we knew about was the 4k message size limit<br>
in GCM and that after a POC phase we were going to have to address it.<br>
On Friday I noticed that the server was choking on messages much smaller<br>
than 4K. Turns out that 4K includes all of the metadata around the<br>
message in addition to the payload. I do not think the GCM bridge is a<br>
good tranport for alpha.1 and (if everyone agrees) will be focusing on<br>
the WebSocket based client.<br>
<br>
One thing that this brings up that I didn't see in the AGSYNC Jira<br>
(unless I'm blind) was how to manage the socket-connectivity interaction<br>
on the clients. Basically a protocol / pattern for how we manage the<br>
socket connections when the device gains and loses internet access or<br>
switches networks. (For instance we should probably disconnect and<br>
reconnect when the device leaves a cellular network and joins a Wifi<br>
network)This is separate from collision handling/detection which does<br>
have a Jira. If there isn't one (a connection handling Jira) should I<br>
make one?<br>
<br>
Happy Monday y'all,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Summers Pittman<br>
>>Phone:<a href="tel:404%20941%204698" value="+14049414698">404 941 4698</a><br>
>>Java is my crack.<br>
<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>
</font></span></blockquote></div><br></div>