<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 29, 2015 at 2:32 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Jul 29, 2015 at 8:28 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</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">Right,<div>we use that mainly because Google does not publish their stuff to maven central. If they would do, we would use that, and perhaps would have also used slightly updated versions.</div><div><br></div><div>I was expecting that this dependency needs to go for GCM3 support (e.g. for using topics). </div><div><br></div><div>But, instead of including the GCM-server source into UPS, why not just release it to a custom maven repo (like done in the given URL).</div><div>If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd party repo. <br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">So it looks like UPS is using a jar packaged by "theganyo" <a href="https://github.com/theganyo/gcm-server" target="_blank">https://github.com/theganyo/gcm-server</a> for its Google stuff. This appears to be a fork of Google's GCM code which was put into maven central. It is also about two years out of date.<div><br></div><div>The fork appears to be based on the code here : <a href="https://github.com/google/gcm" target="_blank">https://github.com/google/gcm</a>.</div></div></div></div></blockquote></div></div></blockquote><div><br></div></span><div><a href="https://github.com/google/gcm/tree/master/client-libraries/java/rest-client/src/com/google/android/gcm/server" target="_blank">https://github.com/google/gcm/tree/master/client-libraries/java/rest-client/src/com/google/android/gcm/server</a><br></div><div><br></div><div>For the XMPP support, we may wanna do for UPS 1.2.x, they don't have anything on github ? </div></div></div></div></blockquote><div><br></div><div>All things considered, Google's code in github for GCM support is rather anemic. I was noticing it didn't have any topics specific stuff in it either. I don't want to say "Let's roll our own" but forking,enhancing, and self hosting might be a good idea.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="HOEnZb"><font color="#888888"><div><br></div><div>-M</div></font></span><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><br></div><div>For implementing topic support I am probably going to need some functionality from Google's actual code. Even if I don't I am going to need things feature in neither repository (Constants for error messages in response to topic messaging are immediately apparent).</div><div><br></div><div>I am looking for brainstorming around the best way to gracefully move this functionality forward. I'm thinking drop the ganyo dependency and code and pull the current Google code into UPS. It is apache licensed.</div><div><br></div><div>Thoughts, fears, tomatoes?</div><span><font color="#888888"><div><br></div><div>Summers</div></font></span></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><span><font color="#888888"><br></font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>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>
</font></span></div>
</blockquote></span></div><span class=""><br><br clear="all"><div><br></div>-- <br><div>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>
</span></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></div></div>