Daniel Henninger wrote: > Hi folk, > > Today I was having a discussion with another developer about one of the > 'standards' that's been in place for a little while and it got me > waffling back and forth as to whether it's a "good" standard or not. > I'll get right to the point: > > MSN username: [EMAIL PROTECTED] > Jabber MSN translated JID: [EMAIL PROTECTED] > > So where did this use of % come from? It seems to work out well, and > has been used in many places, but I don't see it in any XEPs or anything > like that (nothing formal).
We talk about it in XEP-0100, no? > By the same token, if you look at XEP-0106, > it seems like what -should- have happened is: > > Jabber MSN translated JID: [EMAIL PROTECTED] > > Now if a client 'renders' that, it looks like > [EMAIL PROTECTED]@msn.jabber.fake.org, which is a tad confusing looking > in it's own right. True. We need full s2s with all IM networks. Don't hold your breath. :-) > Also, if you are typing a jid on the command line, > assuming you had a command line client, that would be a pain to type. So don't use the command line. ;-) > The argument there as that the client should handle the translation > before sending it off to an XMPP server.. ie I would actually type > [EMAIL PROTECTED]@msn.jabber.fake.org. I think the end user would never type the JID. The end user would be presented with an interface like this: 1. Choose a network: - AIM - ICQ - Jabber - MSN - Yahoo 2. Type an address: __________________ The client then adds the \40 (or old-style %) if needed based on the network. > Such things are a little > confusing to look at, and possibly to parse, but which is "better"? > Obviously \40 appears to be the formal way as it's in an actual XEP. That would be the best way to handle things in the future, I think. > So should those of us in the transport developing world begin the > process of moving from % to \40? IMHO yes. > Where did % come from? Why is it a pseudo standard to date? It's also been used in the email world etc. It's an ugly hack but it works (sort of). /psa
smime.p7s
Description: S/MIME Cryptographic Signature
