-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today in the xmpp:[email protected] room we had a bikeshed discussion about the various transitions in Chat State Notifications (XEP-0085)...
http://logs.jabber.org/[email protected]/2009-08-26.html#15:12:36 I suggest that the following are the most common/sensible transitions: o (start) | | INACTIVE <--> ACTIVE <--> COMPOSING <--> PAUSED | | | | +---<---<---<---<---<---<---<---<---<---+ Someone suggested that you might want to do things like go from <inactive/> to <paused/> if a user returns to a chat session interface containing an unfinished message. I have no deep objection to such a transition, though it strikes me as a bit odd. My reasoning is that the <active/>, <inactive/>, and <gone/> states refer to the overall chat session interface whereas the <composing/> and <paused/> states refer to the message input interface (and are in some sense a subset of <active/>, so that you would go from <paused/> to <inactive/> but from there back to <active/> and then <composing/>). As I said this is painting the bikeshed and I'd just as soon leave the supported state transitions up to the implementation so that we don't need to argue about the spec all the time, but if people care about this I will update the spec. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqVxWYACgkQNL8k5A2w/vxqngCfXbSVijYzCF4IGodMpl+8EOcF RY4AnjPFnO/1XfaZQj6aYvOK/Mayd0/h =fqfx -----END PGP SIGNATURE-----
