[aerogear-dev] Chrome Push Messages
lukas.fryc at gmail.com
Wed Aug 27 14:15:28 EDT 2014
it would be ideal if we could just use the same variant!
I would say we should preserve the compatibility with 1.x as long as it
does not make much efforts to keep both supported.
If it would be too much hassle, let's remove it in 1.1.
Chrome is updated pro-actively anyway, so no one will hear about the old
API in few months.
On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist <lholmqui at redhat.com>
> 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
> the TL;DR of it is, it’s basically the same as Android now.( no more
> refresh tokens and access tokens and such )
> 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.
> 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
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aerogear-dev