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
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.
i had something, now i forgot what it was, need to go back and check
On Fri, Feb 14, 2014 at 2:06 PM, Lucas Holmquist
<lholmqui@redhat.com> wrote:
still exploring
:-) any recent thoughts on 'encodeURIComponent()' ?
On Wed, Feb 12, 2014 at 2:30 PM, Lucas Holmquist
<lholmqui@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 Tue, Feb 11, 2014 at 7:15 PM, Sebastien Blanc
<scm.blanc@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 :
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@apache.org> wrote:
On Thu, Feb 6, 2014 at 3:11 PM, Sebastien Blanc