On 26 May 2010 17:16, jesus salas <[email protected]> wrote:
> Hi Alex,
>
> I trust it works, don't need to test :)
>
> > The same thing happens if, say, someone deletes a paragraph of text that
> > another participant is typing in: in-flight typing is nullified.
>
> Just to clarify, because I use "Delta" where I wanted to use "Delta-
> Operations", I'm sorry.
>
> If delta has several operations, (for instance a Search & Replace
> operation in edtior can generate a Delta with N operations modifying
> several different points in document), what really is nullified
> (cancelled or noop), are operations themselves and not full delta, if
> all operations from a delta are noop'ed then full delta is nullified
> and operation count will be Zero, if not Delta will contain operation
> transformed to the right document space.
>
Mostly right. Neither the delta or the ops are "cancelled" such that they
cease to exist, but the operation targeting the deleted insertion point
transforms to an empty operation: a no-op. The delta's op count won't
change.
>
> For this rule also I want to ask if this matchs G.Wave OT
> implementation
>
> Original Document Space(0)
> D1 and D2 were both generated on O(0)
>
> O(0) "Hello world!"
>
> ( Dd1 and D2 delete region overlap )
>
> D1: skip 5 delete 2:
> ApplyDeltaToDocument: (O(1) 0 "Hello orld!")
> D2: skip 5 delete 6:
> D2 out of sync
> D2 OT against (D1)
> D2' = skip 5 delete 6
> ApplyDeltaToDocument: (O(2) after D2 = "Hello!")
>
>
>
> What means if second delta "delete" over a region previously delete by
> source operations for OT, matching region should be "cancel" than can
> lead to complete or partial operation cancel,
>
> is this right?
>
Similar again. The region of the deletion that is deleting already-deleted
items is transformed away. The transformed D2 would be {skip 5 delete 4}.
>
> thank you in advance
>
> Kind Regards
> jesus
> wave-vs.net
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 26 mayo, 07:58, Alex North <[email protected]> wrote:
> > Yes. A <thread> element inserted as a child of <blip id="b+a">
> concurrently
> > with the deletion of the blip element is nullified in transform. You can
> > probably reproduce this on Google Wave by opening the same wave in two
> > browsers and performing those actions simultaneously.
> >
> > The same thing happens if, say, someone deletes a paragraph of text that
> > another participant is typing in: in-flight typing is nullified.
> >
> > Cheers,
> > Alex
> >
> > On 25 May 2010 21:27, jesus salas <[email protected]> wrote:
> >
> >
> >
> > > Hi,
> >
> > > I want to check how current implementation for Google Wave is managing
> > > "delta cancellation"
> >
> > > On my current implementation if one delta "A", is send to the server
> > > and local copy is "out of sync", (there are some pending deltas to
> > > apply on local document from other participants), and one of the
> > > pending deltas after applying to local document has remove original
> > > "insertion point" for "A", should OT "cancel" "A" delta converting it
> > > to "noop"?
> >
> > > For instance, on below conversation:
> >
> > > I reply to b+a, but owner send a delta deleting completely "b+a" that
> > > has not yet applied to my local document space, then as insertion
> > > point does not longer exists should "reply to b+a" delta be cancelled?
> >
> > > <conversation sort="m">
> > > <blip id="b+a"> <!-- first message -->
> > > <thread id="3Fsd">
> > > <blip id="b+aaa"></blip> <!-- indented reply to "b+a" -->
> > > <blip id="b+aab"></blip> <!-- continuation to "b+aaa" -->
> > > </thread>
> > > <thread id="jjKs">
> > > <blip id="b+aba"></blip> <!-- another reply to "b+a" -->
> > > </thread>
> > > </blip>
> > > <blip id="b+b"> <!-- continuation after "b+a" -->
> > > <peer id="chess+4342"></peer> <!-- consistency peer id -->
> > > <thread inline="true" id="J362">
> > > <blip id="b+baa"></blip> <!-- inline reply to "b+b" -->
> > > <blip id="b+bab"></blip> <!-- continuation to "b+aaa" -->
> > > </thread>
> > > <thread inline="true" ... > <!-- another inline reply group,
> > > possibly at the same location -->
> > > ...
> > > </thread>
> > > <thread id="9dKx"> <!-- non-inline reply to "b+b" -->
> > > ...
> > > </thread>
> > > </blip>
> > > </conversation>
> >
> > > Kind regards
> > > jesus salas
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Wave Protocol" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected]<wave-protocol%[email protected]>
> <wave-protocol%2bunsubscr...@googÂlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/wave-protocol?hl=en.- Ocultar texto de
> la cita -
> >
> > - Mostrar texto de la cita -
>
> --
> You received this message because you are subscribed to the Google Groups
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<wave-protocol%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/wave-protocol?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
