[Standards] Entity Capabilities 2.0

Jonas Wielicki jonas at wielicki.name
Mon Feb 12 08:12:02 UTC 2018

On Montag, 12. Februar 2018 08:45:23 CET Evgeny Khramtsov wrote:
> Mon, 12 Feb 2018 00:41:54 +0100
> Christian Schudt <christian.schudt at gmx.de> wrote:
> > - I am also missing a cache which maps entities to capabilities, i.e.
> > JIDs to disco#info objects. This is the whole point of the XEP (to be
> > able to know an entity’s abilities without service discovery). This
> > cache should be probably be non-persistent. The "Capability Hash
> > Cache“ (hash -> disco#info) is actually only the
> > intermediate/auxiliary cache.
> I think the XEP doesn't solve the main problem of cache invalidation
> and that's why I think it's pointless and I'm not going to implement it
> until the invalidating rules are described.

Could you please be specific which cache you’d like to see properly 
invalidated? Do you mean the (hash -> disco#info) cache or the (entity JID -> 
hash / disco#info) cache?

kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180212/cc41380b/attachment-0001.sig>

More information about the Standards mailing list