On Tue, Jul 29, 2014 at 4:29 PM, Daniel Bevenius <daniel.bevenius(a)gmail.com>
wrote:
> but in our message handler, our notification that is sent back
includes
the channelId and version
The 'Notification' section SimplePush Protocol [1] it specifies what
should be returned. I'm not sure if Mozilla's server does something
different of if it is the client side that does something different.
their live server returns exactly what has been spec'd in [1]
-Matthias
I'm not against changing things, but I think it makes sense for
us to
follow their protocol. I'll read up on the protocol and see if there is any
new information that I'm not aware of. I'll take a look at their server
too.
[1]
https://wiki.mozilla.org/WebAPI/SimplePush/Protocol#PushServer_-.3E_UserA...
On 29 July 2014 16:10, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> so this sort of relates to this thread here:
>
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Differences-betwee...
>
> from
>
https://developer.mozilla.org/en-US/docs/Web/API/Simple_Push_API#Add_the_...
> Moz example
>
> window.navigator.mozSetMessageHandler('push', function(e) {
> console.log('My endpoint is ' + e.pushEndpoint);
> console.log('My new version is ' + e.version);
> //Remember that you can handle here if you have more than
> //one pushEndpoint
> if (e.pushEndpoint === emailEndpoint) {
> emailHandler(e.version);
> } else if (e.pushEndpoint === imEndpoint) {
> imHandler(e.version);
> }
> });
>
> The notification that they send back includes the pushEndpoint and the
> version
>
> Currently, when we do navigator.push.register() the result we send back
> is an object that includes the pushEndpoint, this is actually changing to
> be more in line with Mozilla. Instead of the object being sent back, we
> will send back the pushEndpoint as a String. <--- is a super easy change
> that sebi already did, just need to re-merge it back in
>
> but in our message handler, our notification that is sent back includes
> the channelId and version
>
> I believe the server should now be sending the pushEndpoint in the
> notification instead.
>
> I'd do it myself, but you know, it's java
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf