-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 3/21/12 8:33 AM, Mark Rejhon wrote: > On Tue, Mar 20, 2012 at 1:32 PM, Mark Rejhon <[email protected] > <mailto:[email protected]>> wrote: > > On Mon, Mar 19, 2012 at 2:17 PM, Mark Rejhon <[email protected] > <mailto:[email protected]>> wrote: > > Version 0.2 of XEP-0301 (In-Band Real Time Text) has been > released. [snip] > > URL: http://xmpp.org/extensions/xep-0301.html > > [snip] ChangeLog Summary: [snip] - Add "Multi-User Chat", > "Simultaneous Logins", "Usage with Chat States", and several other > sections > > > From testing my RealJabber software (demonstration XEP-0301 > client), in terms of Chat States > http://xmpp.org/extensions/xep-0301.html#usage_with_chat_states > > XEP-0085 (http://xmpp.org/extensions/xep-0085.html) specifies not > to transmit <composing/> repeatedly. That said, many chat programs > such as Google Talk (GMAIL) and Pidgin, Adium, etc, automatically > assume <active/> for any <message/> transmitted without an XEP-0085 > chat state. This is never properly clarified in XEP-0085 > behaviour, about how to handle <messages/> not containing a chat > state and what assumptions may safely be made. Therefore, XEP-0301 > recommends transmitting a <composing/> with every <message/> that > contains a <rtt/> but without <body/> to maintain backwards > compatibility with existing chat software. > > > To clarify with an example of combining XEP-0085 and XEP-0301 > (which is simply early transmission of your typing before <body> is > transmitted): > > <message to='[email protected]' from='[email protected]/orchard' > type='chat' id='a01'> <rtt xmlns='urn:xmpp:rtt:0' seq='0' > event='new'> <t>Hello, </t> </rtt> <composing/> </message> > > <message to='[email protected]' from='[email protected]/orchard' > type='chat' id='a02'> <rtt xmlns='urn:xmpp:rtt:0' seq='1'> <t>my > </t> </rtt> <composing/> </message> > > <message to='[email protected]' from='[email protected]/orchard' > type='chat' id='a03'> <rtt xmlns='urn:xmpp:rtt:0' seq='2'> > <t>Juliet!</t> </rtt> <composing/> </message> > > <message to='[email protected]' from='[email protected]/orchard' > type='chat' id='a04'> <body>Hello, my Juliet!</body> <active/> > </message> > > > As you can see, I have had to include <composing/> with every > <rtt/> because not including <composing/> is automatically assumed > by a majority of clients to be <active/> if an XEP-0085 chat state > is missing from a <message/>
I see your point. When XEP-0301 advances to Draft, we'll want to update XEP-0085 as well. Essentially, a message with <rtt/> but no <body/> is something in between a content message and a standalone message, in the terminology of XEP-0085. We could think of it as an interim message, and XEP-0085 doesn't talk about such messages because we hadn't defined them back in 2003-2005. 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/ iEYEARECAAYFAk9p6vcACgkQNL8k5A2w/vy55QCg2QwEj8YRhYpcd1jZFa3dzvif eVMAoILwXxt8ZvD+4jyvzzoB3ByOk+4E =uFoD -----END PGP SIGNATURE-----
