[Standards-JIG] proto-JEP: SVG Whiteboarding

[Boyd Fletcher]

On 8/25/06 9:35 AM, "Joonas Govenius" <joonas.govenius at gmail.com> wrote:

>
>> 
>> I had another thought about that.  The "afterId" and "beforeId" are
>> typically used for reordering an element's Z-order position in the DOM
>> tree.  If we change the rule for "parentId" to read "If a parentID is
>> specified, the element becomes the LAST child of that parent.", this
>> would cover the main use case.  When you draw to a "layer" or a
>> specified parent element, you typically append the new element to the
>> end of the child list.  So in an instance like this, neither
>> simultaneous element would be rejected:
>> 
>> <g id="1"/>
>> 
>> User 1 sends:
>> <rect parentId="1" .../>
>> 
>> User 2 sends:
>> <ellipse parentId="1" .../>
>> 
>> Regardless of which one the server processes first, both will be
>> appended as the "last" child of the "g" element, one after the other
>> without breaking any rules.
> 
> That works when you have a "broker" like a server component or a
> master user that lets the users know what the "correct" order is.
> 
> I guess it's clear that I don't think requiring a master is ideal...
> 
> Joonas

requiring a master works well for MUC. we could have certainly implement
multiuser chat with lots of peer-to-peer IMs, but the we didn't because a
server component was far more efficient.