[aerogear-dev] Chrome Push Messages

Sebastien Blanc scm.blanc at gmail.com
Wed Aug 27 14:37:23 EDT 2014

On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist <lholmqui at redhat.com>

> Hello,
> now that the 1.0.0-final is pretty much out for the UnifiedPush Server,
>  i’m starting to look at the new API that Chrome apps use for sending push
> notifications.
> the TL;DR of it is,  it’s basically the same as Android now.( no more
> refresh tokens and access tokens and such )

Maybe stupid and totally undoable but could we not use the current Android
infra in UPS also for Chrome Apps, is there any difference ? In this case
we could have a variant type "GCM" (just renaming the android type)  , a
Chrome App Variant will then just be a of the type GCM like an Android

> So the question is,  do we need to have a deprecation period on what is
> currently there?
> The v1 of the chrome pushMessaging api has become legacy and it is
> recommended to use the new stuff.
> https://developer.chrome.com/apps/cloudMessagingV1
> While i have looked to deeply,  it’s possible we can use the same
> “Variant” structure for Chrome Apps,  Since they will be using the same
> Network
> wdyt?
> -Luke
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140827/75136c5f/attachment.html 

More information about the aerogear-dev mailing list