4:10 p.m.
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
4:29 p.m.
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.
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
>
4:37 p.m.
On Jul 29, 2014, at 10:29 AM, 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.
most likely it's the client side code that should be saving the pushEndpoint along
with the channelID and then looking up by the channel ID, and then giving it to the user
this is probably what happens in the native browser code that we are trying to polyfill
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
4:46 p.m.
Yeah, it looks like this is what's happening (at least looking at the
server side of it that is)
On 29 July 2014 16:37, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
On Jul 29, 2014, at 10:29 AM, 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.
most likely it's the client side code that should be saving the
pushEndpoint along with the channelID and then looking up by the channel
ID, and then giving it to the user
this is probably what happens in the native browser code that we are
trying to polyfill
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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
5:59 p.m.
created a JIRA for it
https://issues.jboss.org/browse/AGJS-203
PR coming soon for the client code
On Jul 29, 2014, at 10:46 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com> wrote:
Yeah, it looks like this is what's happening (at least looking at
the server side of it that is)
On 29 July 2014 16:37, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
On Jul 29, 2014, at 10:29 AM, 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.
most likely it's the client side code that should be saving the pushEndpoint along
with the channelID and then looking up by the channel ID, and then giving it to the user
this is probably what happens in the native browser code that we are trying to polyfill
> 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
_______________________________________________
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
5:34 p.m.
PR for this client update is now here:
https://github.com/aerogear/aerogear-js/pull/135
if peeps have time, a review would be welcome.
looking to get this in before i update the push docs and examples for simplePush and
UPS/SimplePush
-Thanks dudes
On Jul 29, 2014, at 11:59 AM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
created a JIRA for it
https://issues.jboss.org/browse/AGJS-203
PR coming soon for the client code
On Jul 29, 2014, at 10:46 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com> wrote:
> Yeah, it looks like this is what's happening (at least looking at the server side
of it that is)
>
>
> On 29 July 2014 16:37, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
>
> On Jul 29, 2014, at 10:29 AM, 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.
>
> most likely it's the client side code that should be saving the pushEndpoint
along with the channelID and then looking up by the channel ID, and then giving it to the
user
>
> this is probably what happens in the native browser code that we are trying to
polyfill
>> 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
>
>
> _______________________________________________
> 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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:17 a.m.
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
3:58 p.m.
On Jul 30, 2014, at 4:17 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
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]
yea, we realized it is probably coming from the native browser code, so i’ve update the
client side to deal with this
https://github.com/aerogear/aerogear-js/pull/135
-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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:16 a.m.
On Tue, Jul 29, 2014 at 4:10 PM, 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
Using the little hack, I am not seeing the pushEndpoint being returned by
their server:
https://gist.github.com/matzew/cbda360d72eaaef75971
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
here is, the JSON I receive w/ the above hack:
{"messageType":"notification","updates":[{"channelID":"d9b74644-4f97-46aa-b8fa-9393985cd6cd","version":3}]}
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
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
6:14 p.m.
On 2014/7/30 1:16 AM, Matthias Wessendorf wrote:
Using the little hack, I am not seeing the pushEndpoint being
returned
by their server:
https://gist.github.com/matzew/cbda360d72eaaef75971
Registration messages carry the pushEndpoint, which is supposed to go to
the App.
Actual Push Notifications don't have the pushEndpoint. The Client (the
bit of SimplePush that the Apps talk to), maps the ChannelID to the App
that requested it and fires the event when it gets an update.
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
here is, the JSON I receive w/ the above hack:
{"messageType":"notification","updates":[{"channelID":"d9b74644-4f97-46aa-b8fa-9393985cd6cd","version":3}]}
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 <mailto:aerogear-dev@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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
6:47 p.m.
On Jul 30, 2014, at 12:14 PM, JR Conlin <jrconlin(a)gmail.com> wrote:
On 2014/7/30 1:16 AM, Matthias Wessendorf wrote:
> Using the little hack, I am not seeing the pushEndpoint being returned by their
server:
> https://gist.github.com/matzew/cbda360d72eaaef75971
>
Registration messages carry the pushEndpoint, which is supposed to go to the App.
Actual Push Notifications don't have the pushEndpoint. The Client (the bit of
SimplePush that the Apps talk to), maps the ChannelID to the App that requested it and
fires the event when it gets an update.
ok, cool, thanks for the info, that’s what i’ve now updated our client polyfill to do
> 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
>
>
> here is, the JSON I receive w/ the above hack:
>
{"messageType":"notification","updates":[{"channelID":"d9b74644-4f97-46aa-b8fa-9393985cd6cd","version":3}]}
>
>
>
> 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
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> 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
3557
days inactive
3558
days old
10 comments
4 participants
participants (4)
-
Daniel Bevenius -
JR Conlin -
Lucas Holmquist -
Matthias Wessendorf