Peter,
Quoting Peter Saint-Andre <[EMAIL PROTECTED]>:
I think it is counter-intuitive.
Logic would hint that domain.com is exact match and @domain.com is a
wild match.
Similar with [EMAIL PROTECTED] is exact match and [EMAIL PROTECTED]/ 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?
Yes, but don't forget that my original proposal was the opposite variant ;-)
(which, hopefully, should not cause serious problems with backward
compatibility, but as Tomasz and you pointed out may be
counter-intuitive for someone)
I suppose that for XEP-136 backward compatibility is not a problem -
it's MUC where most likely it is.
... and we still have another option: attribute 'exactMatch', which is
certainly backward-compatible ...
Good luck! Alexander
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
