I agree, this is a good one. I think the best way would be to somehow extract the logic on the server side and share it between our plugins for mobile optimizations and this XEP. So we can easily improve behavior server side without affecting clients and the protocol.

%kobit Good point. Right now I'm working on it to provide even simple support for 7.1. In fact I'm adjusting MobileV2 (and later maybe MobileV3) to new interface which will be used by CSI and will make it possible to change logic used by CSI. I suppose I will finish basic support for 7.1 tomorrow as I have version ready for testing.

Added support for XEP-0352: Client State Indication by adding new processor @ClientStateIndication@.

It is enabled by default in this version as I think it may be useful on many installations.

ClientStateIndication processor is independent from MobileV1@, @MobileV2 and MobileV3 which means it can be used without enabling this processors.

All processors may be enabled on server at the same time, however it is not recommended for client to use more that 1 processor during single XMPP session.

By default it uses same logic as mobile optimization plugin MobileV2 - which delays delivery of presences while client is in inactive state but keeps only last presence for each full jid.

It is possible to use logic from MobileV1 by adding following line to etc/init.properties file:

sess-man/plugins-conf/urn\:xmpp\:csi\:0/logic=tigase.xmpp.impl.MobileV1

MobileV3 logic is not supported by CSI processor at this point.

%daniel Should I add information about this to documentation or you will add it?

Documentation is ready for push, however 2 questions:

1. Is there a behavior description for MobileV1 and MobileV3?

2. Can ClientStateIndication processor be disabled?

Added Documentation in commit 18dccd5