On 2013-04-08 17:47, XMPP Extensions Editor wrote:
Version 0.8 of XEP-0301 (In-Band Real Time Text) has been released.
URL: http://xmpp.org/extensions/xep-0301.html
There is a bit contradicting information on how to handle the <w/>
element and smoothness of presentation.
In 6.1.2 Preserving key-press intervals, it is said:
"For high quality presentation of real-time text, the original
look-and-feel of typing can be preserved independently of the
transmission interval. This is achieved usingElement <w/> -- Wait
Interval
<http://xmpp.org/extensions/xep-0301.html#element_w_wait_interval>between otherAction
Elements <http://xmpp.org/extensions/xep-0301.html#action_elements>."
This gives an impression that it is important to provide this
look-and-feel of typing.
But in 4.6.3.3 <w/> Wait interval, it is said:
"Upon receiving aBody Element
<http://xmpp.org/extensions/xep-0301.html#body_element>, recipient
clients SHOULD interrupt all pending pauses for the current real-time
message, in order to prevent a delay in displaying the final message."
A similar instruction is found in 6.5 point 3.
This instruction introduces a risk that many times, the end of a message
is presented in a jerky fashion, suddenly abandoning all smoothness.
There may up to 1.4 seconds of buffered typing, ( but more often between
0 and 700 ms ) that 6.1.2 instructs to show immediately.
I think the sentences in 4.6.3.3 and 6.5 point 3 should be deleted, and
let smooth presentation continue until end of message. The reader is
anyway way ahead of any reader not having real-time text, who had
nothing at all to read while the sender composed the message.
I have reacted a couple of times about the jerks at end of message. What
is your experience?
Gunnar
