On Fri, Jul 20, 2007 at 02:41:32PM +0200, Mats Bengtsson wrote: > > >>But then the XEP is wrong since it includes the "/" character to be > >>> escaped. > >No its not, it is specifying escaping of the node portion of the JID, it > >specifically says you must not escape the resource. > > > > It is since you cannot uniquely separate the JID into its > node+domain+resource parts. > You cannot tell which the node part is. In my example > > User JID: [EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/coci > > the node part may be: mats\40home.se\2fcoci\40home.se\2fmats > The problem is escaping both the "@" and "/" and be able to uniquely > identify the > node+domain+resource parts of a JID. I think you can allow to escape either > of these characters but not both.
If you installed some mind-reading device in the users computer you could determine what the user meant :-) Anyway, it's not defined how to escape a full JID, it's just defined how to escape the _node_ part of a JID. The client has to ask for the nodepart in a seperate entry box I guess (or use a MindReader(tm)). What do you need JID escaping for btw.? Robin
