<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>So to follow up on this,</div><div><br></div><div><br></div><div>Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications.</div><div><br></div><div>Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. </div><div><br></div><div>I think we should rename the AndroidVariant.class and related stuff to GCMVariant . </div><div><br></div><div>I created this Task to track the changes, <a href="https://issues.jboss.org/browse/AGPUSH-928">https://issues.jboss.org/browse/AGPUSH-928</a> since we need to deprecate the current Chrome implementation and update the UI’s for the new way.</div><div><br></div><div>i’m wondering for the “Create Variant” dialog, for Android, we would need to change the name to GCM, but for the icon’s i wonder how it would look to put both Android and Chrome icons, side by side</div><div><br></div><br><div><div>On Aug 27, 2014, at 2:19 PM, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div><br class="Apple-interchange-newline">On Aug 27, 2014, at 2:15 PM, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com">lukas.fryc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hey Luke,<div><br></div><div>ad) Variants</div><div><br></div><div>it would be ideal if we could just use the same variant!</div></div></blockquote><div><br></div>yea, it’s looking like it will be the same thing, we might just have to make a note of it on the UI<br><blockquote type="cite"><div dir="ltr"><div><br></div><div><br></div><div>ad) Compatibility</div><div><br></div><div>I would say we should preserve the compatibility with 1.x as long as it does not make much efforts to keep both supported.</div></div></blockquote><blockquote type="cite"><div dir="ltr"><div><br></div><div>If it would be too much hassle, let's remove it in 1.1.</div><div>Chrome is updated pro-actively anyway, so no one will hear about the old API in few months.</div></div></blockquote><div><br></div>exactly, so maybe a warning or something<br><blockquote type="cite"><div dir="ltr"><div><br></div><div><br></div><div>Cheers,</div><div><br></div><div>~ Lukas</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;">Hello,<div><br></div><div>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.</div><div><br></div><div>the TL;DR of it is, it’s basically the same as Android now.( no more refresh tokens and access tokens and such )</div><div><br></div><div>So the question is, do we need to have a deprecation period on what is currently there?</div><div><br></div><div>The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. <a href="https://developer.chrome.com/apps/cloudMessagingV1" target="_blank">https://developer.chrome.com/apps/cloudMessagingV1</a></div><div><br></div><div>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</div><div><br></div><div>wdyt?</div><div><br></div><div>-Luke</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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>_______________________________________________<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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">aerogear-dev mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><a href="mailto:aerogear-dev@lists.jboss.org" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">aerogear-dev@lists.jboss.org</a><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br></body></html>