[Standards] XEP-136 and XEP-59 implementation comments

Peter Saint-Andre stpeter at stpeter.im
Tue Apr 1 19:32:34 UTC 2008

Alexander Tsvyashchenko wrote:
> Tomasz,
> Quoting Tomasz Sterna <tomek at xiaoka.com>:
>>> There's one other idea I have, but it may break backward
>>> compatibility
>>> and I'm not sure if it doesn't break something else: what if JIDs
>>> like
>>> 'domain.com' are treated like 'wildcards' (like it is now), but
>>> '@domain.com' are considered to be exact matches of domain JID (so,
>>> basically, JID with empty user name)?
>>> The same for resources: 'user at domain.com' is treated like wildcard,
>>> but 'user at domain.com/' is exact match of bare JID?
>> I think it is counter-intuitive.
>> Logic would hint that domain.com is exact match and @domain.com is a
>> wild match.
>> Similar with user at domain.com is exact match and user at domain.com/ is wild
>> match.
> Yes, probably, but that would break current behavior for sure, while the
> original approach seems to be less dangerous in this respect ... If
> backward compatibility is not a problem, though, I personally would be
> happy with either way of doing it.

Well, hmm, breaking backward-compatibility is not good, eh?


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080401/ec868771/attachment.bin>

More information about the Standards mailing list