<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 30, 2014, at 12:14 PM, JR Conlin &lt;<a href="mailto:jrconlin@gmail.com">jrconlin@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000" 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 class="moz-cite-prefix">On 2014/7/30 1:16 AM, Matthias Wessendorf wrote:<br></div><blockquote cite="mid:CAAg5f2SGPusHP20+sHscfDDRk2FsD=QqWAsKeqYAemih98evqA@mail.gmail.com" type="cite"><div dir="ltr">Using the little hack, I am not seeing the pushEndpoint being returned by their server:<div class="gmail_extra"><div class="gmail_quote"><div><a moz-do-not-send="true" href="https://gist.github.com/matzew/cbda360d72eaaef75971">https://gist.github.com/matzew/cbda360d72eaaef75971</a><br></div><div><br></div></div></div></div></blockquote>Registration messages carry the pushEndpoint, which is supposed to go to the App.<br>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.<span class="Apple-converted-space">&nbsp;</span><br></div></blockquote><div><br></div><div>ok, cool, &nbsp;thanks for the info, &nbsp;that’s what i’ve now updated our client polyfill to do</div><div><br></div><div><br></div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000" 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;"><blockquote cite="mid:CAAg5f2SGPusHP20+sHscfDDRk2FsD=QqWAsKeqYAemih98evqA@mail.gmail.com" type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><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; position: static; z-index: auto;"><div style="word-wrap: break-word;"><p style="margin: 15px 0px; color: rgb(51, 51, 51); font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25.5px;">Currently, when we do&nbsp;<code style="font-size: 12px; margin: 0px; border: 1px solid rgb(221, 221, 221); border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px; padding: 0px; background-color: rgb(248, 248, 248);">navigator.push.register()</code>&nbsp;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. &lt;--- is a super easy change that sebi already did, just need to re-merge it back in</p><p style="margin: 15px 0px; color: rgb(51, 51, 51); font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25.5px;">but in our message handler, our notification that is sent back includes the channelId and version</p></div></blockquote><div><br></div><div>here is, the JSON I receive w/ the above hack:</div><div><span style="color: rgb(48, 57, 66); font-family: Menlo, monospace; font-size: 11px; white-space: pre-wrap;">{"messageType":"notification","updates":[{"channelID":"d9b74644-4f97-46aa-b8fa-9393985cd6cd","version":3}]}
              </span><br></div><div><br></div><div>&nbsp;</div><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;"><p style="margin: 15px 0px; color: rgb(51, 51, 51); font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25.5px;">I believe the server should now be sending the pushEndpoint in the notification instead.</p><p style="margin: 15px 0px; color: rgb(51, 51, 51); font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25.5px;">I'd do it myself, but you know, it's java</p></div><br>_______________________________________________<br>aerogear-dev mailing list<br><a moz-do-not-send="true" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br><a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>--<span class="Apple-converted-space">&nbsp;</span><br>Matthias Wessendorf<span class="Apple-converted-space">&nbsp;</span><br><br>blog:<span class="Apple-converted-space">&nbsp;</span><a moz-do-not-send="true" href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions:<span class="Apple-converted-space">&nbsp;</span><a moz-do-not-send="true" href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter:<span class="Apple-converted-space">&nbsp;</span><a moz-do-not-send="true" href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div><br><fieldset class="mimeAttachmentHeader"></fieldset><br><pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre></blockquote><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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></blockquote></div><br></body></html>