[Standards] XEP-0369 (MIX): Early stages of a clients connection

Jonas Wielicki jonas at wielicki.name
Wed Jun 14 06:23:06 UTC 2017


On Mittwoch, 14. Juni 2017 08:17:22 CEST Jonas Wielicki wrote:
> I‘m still not happy with the extra round-trip required by the server for
> discovering the feature before responding with the roster, but from
> discussion in xsf@ (if I recall correctly, mainly with Dave), this may be a
> general problem we’d like to solve in a different protocol (like gratuitous
> entity capabilities sent by clients to the server before presence or
> something similar).

To clarify, the extra round-trip I’m talking about stems from:

From <https://github.com/xsf/xeps/compare/
master...stevekille:MIX#diff-46551996fe454185b68cb3f084c2e18fR2541>:

> A server following the MIX specification MUST determine whether or not a 
> client supports MIX.     If the server does not have this information it 
> MUST use service discovery to determine it before providing roster 
> information.

The other solution for that would be what other protocols which modify server 
behaviour such as Message Carbons do: Have the client explicitly enable it.

kind regards,
Jonas
-------------- 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/20170614/8cd386a2/attachment.sig>


More information about the Standards mailing list