Peter Saint-Andre wrote: [...]
But what if we need to escape a character that is not allowed by STRINGPREP ?
What character? The stringprep profiles used by XMPP are pretty liberal in the characters they allow.
Well, I don�t really know. I didn�t read carefully the STRINGPREP rfc so I just assumed that it might exist some character allowed on some IM network which might not be allowed by STRINGPREP.
[...]
and given that Sametime usernames are case sensitive I needed to escape also all uppercase letters.
Ick.
And thats not all. For example my sametime server reports my username as "CN=Hern�n Tylim/O=Novamens". Imagine now how it looks when escaped...
I implemented jabber:iq:gateway so I hope that an end user will never need to enter (or see) one of these jids.
Does JEP-106 cover this case ? If not, why not ?
Not yet, probably because we didn't think about the need to handle foreign addresses that are case-sensitive for US-ASCII characters. Obviously the intent of JEP-0106 was to handle characters that are not allowed by nodeprep, not to provide a mechanism for getting around the nodeprep/stringprep rules themselves.
It seems that we may need to work on this some more. One possibility is to change MUST NOT to SHOULD NOT regarding which characters can be
transformed using JEP-0106, but I am not sure that's a good idea.
Further thought required....
I hope that this new scenario will serve then as food for thought. In the meanwhile I am using the URL escape mechanism but I would really prefer to use a recognized JEP.
Thanks for the feedback!
Regards, Hern�n
_______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
