On Wed Mar 2 13:11:16 2011, Gregg Vanderheiden wrote:
Interesting issues - thanks
Will reply after examining these issues a bit more - to provide
more complete and concise replies. But some are new topics/issues.
Thanks for hightlighting them.
You know, this entire protocol becomes a lot more palatable to me if
it's reframed somewhat.
The current <rtt/> tag syntax is really very complex, and at the same
time very simgle purpose. Yet what it's doing is, fundamentally,
quite generic - it's doing remote editing.
I think if this were seperated out - and this implies adding more to
it, in particular operational transform - then the remote editing
portion becomes interesting in its own right, and the real-time text
is a simple application of it - that is, real-time text becomes a
sequence of remote document creation, editing, and completing.
We could then also build a true collaborative text editor protocol
just by framing the editing protocol slightly differently.
It should, I think, also become possible to observe lost messages (by
examining the state vector), so that we could easily have a
NACK-based system for error handling - I don't think this is really
needed, given XEP-0198, but it may be useful.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
