Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion How about data format versioning per engine?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Edward Lee  
View profile  
 More options May 16 2009, 10:30 pm
From: Edward Lee <edi...@gmail.com>
Date: Sat, 16 May 2009 21:30:19 -0500
Local: Sat, May 16 2009 10:30 pm
Subject: Re: How about data format versioning per engine?
On Sat, May 16, 2009 at 10:12 AM, Wladimir Palant
<trev....@adblockplus.org> wrote:
> integrity in Weave is wiping server data every time there is a
> mismatch between Weave version

Right now for these early versions of Weave, we're perhaps wiping more
often than necessary because we bump up the version and cause
mismatches. But eventually we'll want to bump the weave version
without changing the server version number.

> I guess this solution is good enough - but only if all data comes from the Weave extension itself.

Part of the reason for wiping is that base record structure might
change -- independent of the engines. For example, we changed how
deleted records were stored on the server, and that would be
incompatible for all engines.

> As soon as other extensions start registering their engines there will be trouble.

Engines could make use of their own versioning and decide to wipe on
their own. But actually, engines can put an-opaque-to-weave version
field in each record that it uploads, and the engine can decide what
to do with different version numbers.

But currently none of the built-in engines do that, so perhaps we
might incorrectly decide to bump the weave server version just because
we changed a built-in engine. (I don't think that line of reasoning
has happened before, but that's only because we bump up  the version
every time.)

Dan: Down the line, what types of changes would warrant a weave server
version bump?

Either way, it might be a good idea to incorporate versioning into the
built-in engines.

Ed


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.