[Standards] whiteboarding and shared editing

Joonas Govenius joonas.govenius at gmail.com
Sat Aug 25 13:11:31 UTC 2007

On 8/24/07, Bishop, Michael W. CONTR J9C880 <Michael.Bishop at je.jfcom.mil> wrote:
> We also spent some time looking over the SXDE documentation again and the proof associated
> with it.  How are conflicts presented to the user?  If we both edit the same element at the same
> time, how is the user informed?  How does the client know what to assign to the element?  In
> short, how is this problem resolved with respects to UI and user feedback?

The protocol dictates that the conflicting results must be undone but
beyond that I don't think it's really the protocols business to define
how the user should be notified. I guess a reasonable way would be to
have some kind of a "tooltip" kind of notification pop up in the area
affected by the collision.

> One thing I'm not clear on, how does your document synchronize when two elements are added
> at once?  Given an arbitrary parent element, what happens if I (User A) add Element A and send
> it to User B?  At the same time, User B adds Element B and sends it to User A?  The following
> could occur:
> User A:  <parent><A/><B/></parent>
> User B:  <parent><B/><A/></parent>
> I guess you can hope the z attribute is different, but is it guaranteed?

Right, the primary way for determining the order is the sxde:z
attribute, the elements are just ordered in an ascending order.
Perhaps a better name for the "z" attribute would be "weight"; heavier
elements sink.

However, like you say, it's not guaranteed that the "z" attributes are
different so there's a secondary (arbitrary) way of determining the
order of two elements with the same "z" value by comparing their id's
and determining which id is "bigger". Doesn't really matter how
"bigger" is defined but you can see in
http://www.xmpp.org/extensions/inbox/sxde.html#glossary what I though

> How are the issues implemented from a user perspective?  Do you have a working
> implementation to look at?

There's an implementation but "working" would probably be an exaggeration :)

Seriously though, I haven't had time to work on the code for a long
time so, although the code is in Psi svn, I don't think it even
compiles right now due to other changes in Psi.


More information about the Standards mailing list