[jdev] Necessity of stringprep support for the client

[Peter Saint-Andre]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/16/12 6:42 AM, Sergey Dobrov wrote:
> On 08/16/2012 07:37 PM, Peter Saint-Andre wrote:
>> On 8/16/12 6:13 AM, Sergey Dobrov wrote:
>> 
>> Agreed, I don't think the ecma thing is usable yet, but I wanted 
>> people here to know that folks are working on solutions.
> 
> Nice to hear! But what option is the best for now? Forget about 
> stringprep? Deliver tables to the client? Use an external service?

Well, it is the server's responsibility to enforce the address format
rules (including internationalization or "i18n" for short) where
possible, however sometimes clients communicate with each other in
situations where the server is just an XML router. So ideally the
client will be able to generate JIDs and JID-parts that conform to the
rules. Unfortunately, right now there really are no good options for
JavaScript clients: there are no comprehensive libraries (although we
might want to do more research in this area) and we haven't defined
any external services for this (e.g., send a string to your XMPP
server and have it return a conformant JID or JID-part). Although a
service like that would be helpful, it might be more productive to
work on better i18n support in JavaScript.

> Also, thanks for the information about PRECIS and for the feedback
> as is. :)

Sure thing. Reviews of draft-ietf-xmpp-6122bis would be appreciated. :)

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAtAq8ACgkQNL8k5A2w/vx2CACfbMYAlmcRWKS+5XXrLGqLPQUp
VakAoKkUcTC1owGg5lKiPh38+Bu64ppp
=htRo
-----END PGP SIGNATURE-----