[aerogear-dev] Differences between Firefox OS "native" Push lib and AeroGear's Push adapter

Daniel Bevenius daniel.bevenius at gmail.com
Fri Jul 25 05:04:31 EDT 2014


>5. don’t use the url as a deviceToken (might not comply with Mozzila’s
SimplePush specs)
The deviceToken is an UPS concept and there is nothing in the SimplePush
spec which is violated in this case.

I'm not sure about what the best option is for UPS thought. Would a regex
in for the @Path annotation work perhaps, something like:

@DELETE
@Path("{token, .+}")
public Response unregisterInstallations(


On 25 July 2014 10:32, Tadeas Kriz <tkriz at redhat.com> wrote:

>
>> Tadeas Kriz
>
> On 24 Jul 2014, at 05:44 pm, Karel Piwko <kpiwko at redhat.com> wrote:
>
> > On Thu, Jul 24, 2014 at 3:28 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
> >>
> >> It should not. For hibernate, it’s just a string like any other.
> >> The problem might be in the configuration of JAX.RS/RestEasy. If
> >> I’ll have some time today evening, I’ll try to fix it, it should
> >> be an easy fix.
> >
> > Last famous words? ;-)
> >
>
> I shall never say “an easy fix” again.
>
> > But I agree. Everything is string and URL encode should happen on
> > client while server should automatically decode and work always with
> > just decoded string. If we need to encode twice, something is wrong.
> >
>
> Anyway, the 400 Bad request response is made by the tomcat itself,
> disallowing the use of %2F as a path parameter. This will probably apply on
> other web containers.
>
> Possible solutions with their disadvantages:
>
> 1. well-documented double-encoding of the URL (might be confusing)
> 2. use @QueryParam instead of @PathParam (breaks the api consistence, as
> every other call would still use @PathParam)
> 3. allow @QueryParam (again, breaks the api consistence, but only for the
> SimplePush)
> 4. find another encoding (Base64 for URL = URLEncode then Base64 encode)
> 5. don’t use the url as a deviceToken (might not comply with Mozzila’s
> SimplePush specs)
>
> What do you think guys?
>
> >>
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140725/a398e9f9/attachment-0001.html 


More information about the aerogear-dev mailing list