Ok, makes sense as well.
I conclude from this discussion, that there are no extension protocols which
MUST be coupled with another one in service discovery (i.e. if A then B),
although for some they SHOULD (e.g. if urn:xmpp:jingle:transports:ibb:1 then
urn:xmpp:jingle:1).
Thanks.
-Christian
On 16 March 2015 at 23:11, Lance Stout wrote:
> This one may need to go to Peter for a philosophy question: what is to be
> done when an implementation of feature Y MUST support X as a fallback, but
> the user chooses to disable X.
>
MTI != MTD
Mandatory To Implement does not mean Mandatory To
On 16.03.2015 23:06, Christian Schudt wrote:
> Thanks Florian, generally I agree, but please read my answers below.
I was mostly having a modular XMPP client library in mind. Here, if you
advertise support for 'carbons', the library code for forward will be
loaded. And in Smack's case, it's the fu
