Difference between revisions of "XEP-Remarks/XEP-0352: Client State Indication"

Jump to navigation Jump to search
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== No Beacon signaling when the client state changed fully to activated ==

Certain use cases require to determine when the client state has been changed to "activated" (i.e. for most implementation when the last flushed (presence) stanza has been received). Imagine for example an client which determines the receiving JIDs based on presences. First this clients sets CSI to active and then it has to determine somehow when the presence information is up to date.
== Behavior on stream resumption is underspecified ==

It would be sufficient if the server would send a beacon message like
<message to='client@examle.org/resource'>
  <csi xmlns='urn:xmpp:csi:1'>

Latest revision as of 20:46, 17 April 2020

This is a page for information about XEP-Remarks/XEP-0352: Client State Indication, including errata, comments, questions, and implementation experience.

Behavior on stream resumption is underspecified