2009/11/15 Daniel Danopia <[email protected]> > > The issue that I see is when I host waves and the sandbox sends a > submission for an older version. The sandbox seems very picky about > submissions and might not recognize the delta as being the one it > submitted if it's signed by someone else (me) with a different > applied_to version. Plus it'd get the other delta with the same > applied_to as the one it sent to me, which would probably confuse it > further. >
The same problem exists on the client side. When I send a delta to the server I apply it locally immediately and send it to the server. The server will send me a (perhaps transformed) delta back eventually. I need to detect this one because I applied it locally already. The sandbox will have the same problem, I assume. I wonder why there is no ID in deltas. This would at least solve the issue of detecting my own deltas. Torben > On Nov 15, 10:50 am, Torben Weis <[email protected]> wrote: > > In fact the trick is to apply a delta to a newer version if there was a > > conflict. > > > > The server hosting the wavelet is always right. Thus, if a delta > generated > > by your "ruby on sails" client conflicts with a delta sent by the > > wavelet-hosting server, you must transform (!!) your delta thus that it > can > > be applied to a newer version. Just sending out the same delta (without > > transformation) and applying it to a higher version number will sometimes > > work and sometimes not. > > > > In addition, you must have at most one pending delta submit at a time. > Then > > you must wait until this delta is applied by > > the server hosting the wavelet. Now you can submit the next delta. And so > > on. This simplifies the OT process inside the server > > and is a difference between the Jupiter system and Wave. > > > > However, I wonder how to handle signing after transformation. > Transforming a > > delta will invalidate its signature ... > > > > Torben > > > > 2009/11/15 Daniel Danopia <[email protected]> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
