[aerogear-dev] UPS 1.2, GCM 3.0 Topics, and Google's rest-client updates
supittma at redhat.com
Mon Aug 3 12:46:56 EDT 2015
On Mon, Aug 3, 2015 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:
> Hello Summers,
> my concern would be that this repo is Ant based and not available in Maven
> Central. So a fork would indeed be needed. Other problem is that the lib
> does not support supplying backend server location -
What do you mean?
> but this is something a PR can fix. In the past, I believe that we
> evaluated this library as an option as well
> On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
>> Guys and gals,
>> 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
>> 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.
>> Thoughts, comments, tomatoes?
>> 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.
>> * https://github.com/google/gcm/issues/84
>> *** https://github.com/google/gcm/issues/85
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aerogear-dev