[Standards] Entity Capabilities Woes

Peter Saint-Andre stpeter at jabber.org
Thu Mar 15 19:19:27 UTC 2007

Remko Tronçon wrote:
>> Would be the same for most cases - but from protocol point of view : it
>> need not necessarily be the same.
>> Hence, we cache it as a tuple of all three and dont assume that it is
>> same across versions.
> That's what we do as well. But on the other hand, if you can assume
> it, you can cache it by a mapping from disco node
> (http://psi-im.org/caps#0.11, http://psi-im.org/caps#cs) to features,
> making it even easier to implement (and avoiding even more disco
> requests).

Well as my illustrious co-author said, the intent was that ext is stable 
across application versions. If we make that a MUST in the spec then we 
can save more packets. Seems like a good idea to me.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070315/0b6bbf65/attachment.bin>

More information about the Standards mailing list