[Standards] Proposed XMPP Extension: Client State Indication
mwild1 at gmail.com
Tue Aug 19 17:05:07 UTC 2014
On 19 August 2014 17:21, Evgeny Khramtsov <xramtsov at gmail.com> wrote:
> Tue, 19 Aug 2014 11:30:18 +0100
> Matthew Wild <mwild1 at gmail.com> wrote:
>> There are so many different approaches and optimisations (as you just
>> demonstrated in your message!). I don't feel this XEP is the right
>> place to document them, I think there is a lot of room for
>> experimentation. I want to leave implementations up to server
>> developers, deployments and (if the server allows it) client and user
>> preference. If good ones are found, they can be documented in separate
>> XEPs if necessary (and reference CSI).
>> This XEP is just about giving the server more information about when
>> it would be more appropriate to apply some kinds of optimisation.
> I disagree. We need the exact finite state machine (like it's done in
> good RFCs, see SIP transaction FSM or TCP FSM) which gives the
> straightforward way to implement such optimizations. Otherwise I don't
> see the XEP is useful.
You can implement as many finite state machines as you like. But this
is not the XEP for that, this is just to turn them on/off. Let's keep
it simple for once, folks :)
More information about the Standards