Hi there,
I'm maybe a bit out of date on current C/S implementation, so sorry if II
state something wrong here but for what I remember for wave-vs
implementation on this...
Theory for Client Side is to cache you local updates sending one by one to
server while accept WaveletUpdates coming from Se
>
> There's still one thing that's fuzzy in the spec concerning submitted
> deltas and the subsequent delta updates. When a client submits a delta, the
> way it transforms wavelet updates is different depending on whether or not
> the update was applied before or after the submitted delta. If the c
On Mon, Dec 13, 2010 at 5:34 PM, Torben Weis wrote:
> Hi Tad,
>
> this problem was on my mind for a long time.
> Caching updates is not the ideal solution for interactivity and
> collaboration, because updates are unnecessarily delayed.
>
> What a client really needs is a way to detect its own de
Hi Tad,
this problem was on my mind for a long time.
Caching updates is not the ideal solution for interactivity and
collaboration, because updates are unnecessarily delayed.
What a client really needs is a way to detect its own delta when receiving
it as a wavelet update.
Soren told me how to d
