On Sunday 05 February 2006 19:52, Michal Vaner (Vorner) wrote: > Dne neděle 05 únor 2006 08:49 Trejkaz napsal(a): > > Hi all. > > > > I've been looking at knocking together a simple privacy list management > > webapp, which might eventually be of use for all those poor people whose > > clients don't support it directly. > > > > One of the things I just noticed is that ejabberd doesn't list > > jabber:iq:privacy as a feature in service discovery, but jabberd2 does. > > I'm pretty sure ejabberd does support the feature since it claims 100% > > XMPP compliance now, but if it doesn't list the feature then what is the > > proper way to detect its existence? > > XMPP, If I read it properly, does not say it should be listed in the > features. Instead, it says that privacy lists are required, so client sould > not detect the server can do that, client should expect them to do so. If > not, the server is not XMPP compliant and you will get feature not > implemented error when you try do use them.
So basically what you're saying is, the only way to find out is to try and
then get an error, because:
1) a server might be 100% XMPP compliant, and simply allow the privacy list
feature to be disabled, or;
2) a server might not claim to be XMPP compliant at all, and still support
the feature.
IMO, it would be useful if there were a way to find out if a feature exists
before trying to use it (like we have for almost every other feature.)
TX
--
Email: [EMAIL PROTECTED]
Jabber ID: [EMAIL PROTECTED]
Web site: http://trypticon.org/
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
pgpbZhlkvbfWC.pgp
Description: PGP signature
