Ok,<div><br></div><div>So as token, we use the endpointURL, and on client we perform <span style="background-color:rgba(255,255,255,0);font-size:small"> the </span><span style="background-color:rgba(255,255,255,0);font-size:small">encodeURIComponent() </span><span style="background-color:rgba(255,255,255,0);font-size:small">function ?</span></div>
<div><span style="background-color:rgba(255,255,255,0);font-size:small"><br></span></div><div><span style="background-color:rgba(255,255,255,0);font-size:small">-Matthias<span></span></span></div><div><br>On Monday, April 7, 2014, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">so i went back to look at what i had,<div><br></div><div><br></div><div>i don't think we need to get to complicated here,</div>
<div><br></div><div>reading the spec stuff, and this example</div><div><br></div><div><a href="https://wiki.mozilla.org/WebAPI/SimplePush#Client_.28WebApp.29_code" target="_blank">https://wiki.mozilla.org/WebAPI/SimplePush#Client_.28WebApp.29_code</a></div>
<div><br></div><div>they show sending the pushEndpoint to the "App server", so i think we could just use and keep it simple</div><div><br></div><div>it is also recommended that the channelID is never exposed to the application.</div>
<div><br></div><div><br><div><div>On Apr 1, 2014, at 3:34 PM, Lucas Holmquist <<a>lholmqui@redhat.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">i had something, now i forgot what it was, need to go back and check<br>
<div><div>On Apr 1, 2014, at 3:05 PM, Matthias Wessendorf <<a>matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div><br><div>On Fri, Feb 14, 2014 at 2:06 PM, Lucas Holmquist <span dir="ltr"><<a>lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote 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">still exploring</div></blockquote>
<div><br></div><div>:-) any recent thoughts on 'encodeURIComponent()' ? </div><div> </div><blockquote 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"><div><br><div><div>On Feb 13, 2014, at 3:39 PM, Sebastien Blanc <<a>scm.blanc@gmail.com</a>> wrote:</div><br><blockquote type="cite">
<div dir="ltr"><br><div><br><br><div>On Wed, Feb 12, 2014 at 2:30 PM, Lucas Holmquist <span dir="ltr"><<a>lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote 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">i might have a couple thoughts, but i need to try some things out first</div>
</blockquote>
<div><br></div><div>Any update on that or does the solution proposed by Matzew (using <span style="font-size:13px;font-family:arial,sans-serif"> </span><span style="color:rgb(48,57,66);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">encodeURIComponent() ) could be enough ? </span></div>
<blockquote 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">
<div><br><div><div>On Feb 12, 2014, at 3:53 AM, Sebastien Blanc <<a>scm.blanc@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><br>
<div><br><br><div>On Tue, Feb 11, 2014 at 7:15 PM, Sebastien Blanc <span dir="ltr"><<a>scm.blanc@gmail.com</a>></span> wrote:<br>
<blockquote 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 dir="ltr">Ok,<div>I've been doing some tests by using the PushEndpoint as device token. For registration it works but I just faced an issue by trying to unregister because the URL for the DELETE looks like : </div>
<div><br></div><div><a href="https://judconpush-sblanc.rhcloud.com/rest/registry/device/https://updates.push.services.mozilla.com/update/my_personnal_psuhendpoint_id" target="_blank">https://judconpush-sblanc.rhcloud.com/rest/registry/device/https://updates.push.services.mozilla.com/update/my_personnal_psuhendpoint_id</a> [<br>
</div><div><br></div><div>And the REST endpoint get a bit crazy by the extra "/" present in the endpoint URL. Therefore, I think we must just use the last URL fragment as deviceToken.</div></div></blockquote><div>
</div><div>Ok answering to myself ;) That won't work neither since if we do that UPS won't have the compllete push endpoint URL. </div><div>So how do we deal with that ?</div><blockquote 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><div>
<br><br><div>On Thu, Feb 6, 2014 at 3:27 PM, Matthias Wessendorf <span dir="ltr"><<a>matzew@apache.org</a>></span> wrote:<br><blockquote 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 dir="ltr"><br><div><br><br><div><div>On Thu, Feb 6, 2014 at 3:11 PM, Sebastien Blanc <span dir="ltr"></span></div></div></div></div></blockquote></div></div></div></blockquote></div></div></div></blockquote></div></div>
</div></blockquote></div></div></div></blockquote></div></div></div></blockquote></div></div></div></blockquote></div></div></blockquote></div></div></div></blockquote></div><br><br>-- <br>Sent from Gmail Mobile<br>