<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 31 Jul,2014, at 14:30 , Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 31, 2014 at 2:18 PM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br>
<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;">BTW,<br>
<br>
Also the ‘deviceID’ for Microsoft Push will be an URL so we really need a way to fix this. Adding double url encoding is already a form of encoding so why not go for base64 it’s ‘just’ another kind of encoding. I also don’t like the idea of a mapping having it stateless is much nicer IMO, I would rather have some form of encoding.<br>
</blockquote><div><br></div><div>Sounds good. Would you be interested in doing the encoding, as proposed and also work on <a href="https://issues.jboss.org/browse/AGPUSH-833">https://issues.jboss.org/browse/AGPUSH-833</a> (for the unregister issue) ? </div>
<div><br></div></div></div></div></blockquote>I’m on it</div><br></body></html>