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
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
