Real Time Text Notes

Created on 2022-10-12T00:02:24-05:00

Return to the Index

This card can also be read via Gemini.

Handle: identifies a particular element which ocurred in a session.

Sequence number: monotonically increasing identifier. Used to assign a strict order to update events.

Session: open, close. A whole session where zero or more real time text events will be exchanged.

Event: open, close, update. An event is opened and updated until the message is deemed done where it is then closed.

Updates: append, remove, wait.

Append: adds some span of text at a position to an event.

Remove: removes text from a start to an end position.

Wait: inserts a delay.

Events are bundled up to avoid network congestion. Software is allowed to record inputs from the user, coalesce those events, and transmit one bundle per some period of time deemed suitable. "Wait" events allow representing pauses from the input despite the bundled and delayed transmission.

For the best balance between interoperability and usability, the default transmission interval of elements for a continuously-changing message SHOULD be approximately 700 milliseconds. This interval makes it possible for clients to meet ITU-T Rec. F.700 Section A.3.2.1 for good quality real-time text conversation in many network environments. If a different transmission interval needs to be used, the interval SHOULD be between 300 and 1000 milliseconds. (XMPP)