<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 31, 2015 at 5:04 PM, 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"><div dir="ltr">Guys and gals,<div><br></div><div>UPS is currently using a fork of Google's rest-client sample to communicate with Google's servers (See the previous thread UPS and com.ganyo:gcm-server for details**). This is an outdated fork from <a href="https://github.com/google/gcm" target="_blank">https://github.com/google/gcm</a>. </div><div><br></div><div>It is in fact very outdated. The rest client code, Message and Builder objects, Constant fields, and Sender code don't support all of the fields/errors/etc needed for GCM topics messaging. Additionally it uses a deprecated field in a few places. I've filed two* issues*** in the gcm project to reach out and begin work with them to resolve this in a more sane way. In the meanwhile we will probably have to patch and support our own fork of the library.</div><div><br></div><div>Thoughts, comments, tomatoes?</div><div><br></div><div>PS, this will probably bump XMPP support from aerogear-android-push 3.0 and UPS 1.2. Please let me know if it should and i will pull those from the JIRA epics and we can reschedule them.</div></div></blockquote><div><br></div><div>This would a work-around, but ultimately we wanna use (or create) a GCM-XMPP library, to be used in UPS, right ? </div><div><br></div><div>Sure, if that takes a bit more time, let's get this scheduled for 1.3. I think moving to XMPP, will also improve send performance, since we have one connection (pool) instead of countless HTTP requests</div><div><br></div><div>-M</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Summers</div><div><br></div><div>* <a href="https://github.com/google/gcm/issues/84" target="_blank">https://github.com/google/gcm/issues/84</a></div><div>*** <a href="https://github.com/google/gcm/issues/85" target="_blank">https://github.com/google/gcm/issues/85</a></div><div>** <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html</a></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>