[aerogear-dev] Chrome Push Messages

[Lucas Holmquist]

of course we will need to update the UI/examples so they know about it :)


but the user can differentiate between the 2 using the meta data then send back when registering


On Aug 27, 2014, at 2:55 PM, Sébastien Blanc <scm.blanc at gmail.com> wrote:

> 
> 
> Envoyé de mon iPhone
> 
> Le 27 août 2014 à 20:52, Lucas Holmquist <lholmqui at redhat.com> a écrit :
> 
>> 
>> On Aug 27, 2014, at 2:37 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> 
>>> 
>>> 
>>> On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
>>> 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 variant.
>> 
>> I just ran a quick test using an android variant as a "chrome app”,  and all worked perfectly.  was able to register with AeroGear.js to the UPS and get sent a push notification to my chrome app.
>> 
>> no code changes needed on the UPS side of things!!
>> 
>> 
>> We might want to rename the Android Variant to GCM or something similar similar since the network is now used for both types of applications.
>> 
>> This will probably also be the same thing when adding Safari Push notifications since it also uses APN’s,  although there are some slight differences
>> 
>> 
>> So, really,  some one can use the new Chrome API stuff today with the UPS,  they just need to create an Android Variant
> Awesome ! Now we are even more unified and this for free :)
>> 
>>>  
>>> 
>>> 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
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> 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/c9c5d9d4/attachment.html