so after testing this thing out with encodeURIComponent, the delete does work, however,
we need to "double up" the encode.
this works:
On Apr 7, 2014, at 2:09 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
On Apr 7, 2014, at 12:52 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
> Ok,
>
> So as token, we use the endpointURL, and on client we perform the
encodeURIComponent() function ?
i think so( as suggested 2 months ago :) ) i just need to see how this will affect how
we store stuff in LS.
>
> -Matthias
>
> On Monday, April 7, 2014, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> so i went back to look at what i had,
>
>
> i don't think we need to get to complicated here,
>
> reading the spec stuff, and this example
>
>
https://wiki.mozilla.org/WebAPI/SimplePush#Client_.28WebApp.29_code
>
> they show sending the pushEndpoint to the "App server", so i think we
could just use and keep it simple
>
> it is also recommended that the channelID is never exposed to the application.
>
>
> On Apr 1, 2014, at 3:34 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
>
>> i had something, now i forgot what it was, need to go back and check
>> On Apr 1, 2014, at 3:05 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
>>
>>>
>>> On Fri, Feb 14, 2014 at 2:06 PM, Lucas Holmquist <lholmqui(a)redhat.com>
wrote:
>>> still exploring
>>>
>>> :-) any recent thoughts on 'encodeURIComponent()' ?
>>>
>>>
>>> On Feb 13, 2014, at 3:39 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Wed, Feb 12, 2014 at 2:30 PM, Lucas Holmquist
<lholmqui(a)redhat.com> wrote:
>>>> i might have a couple thoughts, but i need to try some things out first
>>>>
>>>> Any update on that or does the solution proposed by Matzew (using
encodeURIComponent() ) could be enough ?
>>>>
>>>> On Feb 12, 2014, at 3:53 AM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Feb 11, 2014 at 7:15 PM, Sebastien Blanc
<scm.blanc(a)gmail.com> wrote:
>>>>> Ok,
>>>>> 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 :
>>>>>
>>>>>
https://judconpush-sblanc.rhcloud.com/rest/registry/device/https://update...
[
>>>>>
>>>>> 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.
>>>>>
>>>>> Ok answering to myself ;) That won't work neither since if we do
that UPS won't have the compllete push endpoint URL.
>>>>> So how do we deal with that ?
>>>>>
>>>>>
>>>>> On Thu, Feb 6, 2014 at 3:27 PM, Matthias Wessendorf
<matzew(a)apache.org> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 6, 2014 at 3:11 PM, Sebastien Blanc
>
>
> --
> Sent from Gmail Mobile
> _______________________________________________
> 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