[jdev] XEP-0115: backward compatibility
alban.crequy at collabora.co.uk
Tue May 6 06:31:52 CDT 2008
Le Tue, 6 May 2008 13:14:06 +0200,
"Remko Tronçon" <remko at el-tramo.be> a écrit :
> > 3. If a client with pluggable capabilities want to be compatible
> > with both remote client implementing the XEP v1.3 and v1.5, is the
> > recommended way to use both 'ext' and 'hash' attributes?
> I don't think combining both makes sense (or will even work properly).
> If you support the new protocol, use the new one only, and do not send
> any 'ext'.
Some legacy clients requires to have the bundle "voice-v1" in "ext".
Theses clients does not check what is inside the bundle, just that
a bundle with this name exist.
This is wrong because the v1.3 XEP did not allow such behaviour:
"The names of the feature bundles MUST NOT be used for semantic
purposes: they are merely opaque identifiers that will be used in other
But in order to remain compatible with theses legacy clients, I have
to add the bundle "voice-v1". So, I am looking for the best way to
implement the new XEP with this requirement.
More information about the JDev