[jdev] Privacy feature
Alexey Nezhdanov
snake at penza-gsm.ru
Sun Feb 5 09:12:17 CST 2006
В сообщении от Воскресенье 05 Февраль 2006 15:42 Trejkaz написал(a):
> On Sunday 05 February 2006 22:54, Alexey Nezhdanov wrote:
> > В сообщении от Воскресенье 05 Февраль 2006 14:09 Trejkaz написал(a):
> > > On Sunday 05 February 2006 21:52, Michal Vaner (Vorner) wrote:
> > > > > So basically what you're saying is, the only way to find out is to
> > > > > try and then get an error
> >
> > I propose next logic:
> > 1) Since only 100% XMPP compliant servers can declare "version='1.0'" in
> > the stream header so decide on it. If there _is_ such attribute then
> > privacy lists are supported.
> > 2) If server have no "version='1.0'" attribute - then look to advertised
> > features.
> >
> > This method is quite complying standart IMHO.
>
> Okay, so...
>
> - If the feature is present, then privacy is available.
> - If the version is not 1.0, then privacy is not available.
> - Otherwise, try and retreive the privacy lists to see if it's available.
No.
- If the version is 1.0 or feature is present then privacy is available;
- otherwise privacy is not available.
> Because for example, gmail.com claims version="1.0" but responds with
> feature-not-implemented when I try to use privacy lists. (BTW, does this
> mean that gmail.com should not be claiming version="1.0"?)
Yes exactly, they should not claim this if they have some core parts
unimplemented.
> TX
So as the resort to the real world you just need to be ready to start with
hard "feature is available" and then react to "not implemented" error.
--
Respectfully
Alexey Nezhdanov
More information about the JDev
mailing list