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

Tomasz Sterna tomek at xiaoka.com
Sun Mar 30 10:33:17 UTC 2008

Dnia 2008-03-30, nie o godzinie 13:20 +0300, Alexander Tsvyashchenko
> 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

  /\_./o__ Tomasz Sterna
 (/^/(_^^' http://www.xiaoka.com/
._.(_.)_   im:smoku at xiaoka.com

More information about the Standards mailing list