Project

General

Profile

Feature #4280

Add support for XEP-0352: Client State Indication

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
2016-06-26
Due date:
% Done:

100%

Estimated time:
Source Code Disclaimer:

Description

Add support for XEP-0352: Client State Indication to client library.

I think it should be preferred over protocol used for mobile optimizations as it is standarized version and optimization logic still may be changed on server side - client do not need to be aware of currently used logic.


Related issues

Related to Tigase Swift XMPP client library - Feature #4279: Add support for XEP-0352: Client State IndicationClosed2016-06-26

Related to Tigase XMPP Server - Task #4244: Add support for XEP-0352: Client State IndicationClosed2016-06-152016-07-31

Associated revisions

Revision e7433a13 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

Task #4280 - added support for XEp-0352: Client State Indication

History

#1 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Related to Feature #4279: Add support for XEP-0352: Client State Indication added

#2 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Related to Task #4244: Add support for XEP-0352: Client State Indication added

#3 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Status changed from New to Closed
  • Target version set to 3.2.0
  • % Done changed from 0 to 100

I implemented support for this XEP as ClientStateIndicationModule which needs to be registered. When it's methods are called then proper notification will be delivered to server. Calling methods active()@, @inactive() or setState(boolean active) needs to be done by client.

Also available in: Atom PDF