On Fri, 2008-01-18 at 16:50 -0700, Peter Saint-Andre wrote: > [..] > > Now you know that node='http://www.chatopus.com' and v='2.1' and > ver='zHyEOgxTrkpSdGcQKH8EFPLsriY=' means a software product name of > "Chatopus" for xml:lang='en' (but for some other language the name could > be different!). So you cache that across sessions and you never need to > send a disco#info or iq:version request to an entity that provides that > combination of node+v+ver in caps. > > To do this we need to include node and v in caps, but we're going to > include node anyway (for backwards-compatibility). So the question is > whether including 'v' is worth the extra 5 or 10 bytes in each presence > notification.
Jumping in at random, too, my observation is that there is the desire to use Entity Capabilities to find out information from another entity beyond capabilities (service discovery identity and features) with minimal traffic. At some point we defined XEP-0128 (Service Discovery Extensions) to hold such additional information and it seems to me that a solution to all this is to include such information to calculate the value of the caps 'ver' attribute. This would require a different method of calculating the hash, though. Obviously, this is only useful if this meta information does not change often and is not too diverse between instances of the same (version) of a client. -- Groetjes, ralphm
