Hi Christian,
Thanks again for your input. Comments inline.
On Dienstag, 13. Februar 2018 23:20:54 CET Christian Schudt wrote:
> Hi Jonas,
>
> > You are referring to the processing entities side? The entity is free to
> > choose from the set as it desires. The order of elements inside the hash
On Montag, 12. Februar 2018 09:10:47 CET Jonas Wielicki wrote:
> On Montag, 12. Februar 2018 00:41:54 CET Christian Schudt wrote:
> > - Generally I am unsure if using the "xml:lang" and „name" from the
> > identities is a good idea at all, because these two attributes should not
> > change the
Hi Jonas,
> You are referring to the processing entities side? The entity is free to
> choose from the set as it desires. The order of elements inside the hash set
> is undefined. It could for example iterate a list of hash functions in
> descending order of preference and look for hashes in
On Montag, 12. Februar 2018 13:53:40 CET Evgeny Khramtsov wrote:
> Mon, 12 Feb 2018 09:12:02 +0100
>
> Jonas Wielicki wrote:
> > 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
On Mon, Feb 12, 2018 at 10:53 AM, Evgeny Khramtsov wrote:
> A server can change configuration in runtime at any time, potentially
> changing its disco#info. How to notify local clients about that? How to
> notify clients from remote servers? How to notify connected servers
Mon, 12 Feb 2018 09:12:02 +0100
Jonas Wielicki wrote:
> 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?
A server can change configuration in
On Montag, 12. Februar 2018 08:45:23 CET Evgeny Khramtsov wrote:
> Mon, 12 Feb 2018 00:41:54 +0100
>
> Christian Schudt 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
On Montag, 12. Februar 2018 00:41:54 CET Christian Schudt wrote:
> - Generally I am unsure if using the "xml:lang" and „name" from the
> identities is a good idea at all, because these two attributes should not
> change the capabilities of an entity. Name and language is just for humans.
> I.e. if
Hi Christian,
First of all, thank you for your thorough feedback. My comments are inline
below.
On Montag, 12. Februar 2018 00:41:54 CET Christian Schudt wrote:
> Hi,
>
> I’ve implemented Entity Capabilities 2.0 (XEP-0390) and like to share some
> thoughts about it here and in the following
Mon, 12 Feb 2018 00:41:54 +0100
Christian Schudt 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
>
10 matches
Mail list logo