From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] silly replica question (repeated m msgs won't go away)
Date: Tue, 10 Feb 2004 19:24:05 +0200 [thread overview]
Message-ID: <20040210192404.T17981@cackle.proxima.alt.za> (raw)
In-Reply-To: <b673b6dbcfc6ae1f421bda788e25becc@terzarima.net>; from Charles Forsyth on Tue, Feb 10, 2004 at 04:10:20PM +0000
On Tue, Feb 10, 2004 at 04:10:20PM +0000, Charles Forsyth wrote:
>
> i don't think i'd describe what replica attempts as `heuristic'.
> there's a little graph of possibilities and it either chooses the safe
> path or requests guidance.
>
I really hope I don't sound confrontational, there's much I don't
know and can only guess at, but there's definitely more than a
trivial amount of slipperiness about replica that makes it unsuitable
for the type of replication that Microsoft used (or used to use)
to propagate changes to the users database between the PDC and BDCs
(if you don't know the acronym, you're missing nothing) or what
Lotus Notes uses (this is NetNews in disguise or is it on steroids?)
or, for that matter, the OpenLDAP replicator.
> an SHA1 hash would be helpful; by using mtime+length it can moan about
> insignificant changes but then again, with some things it's possible
> the mtime matters, and perhaps it should moan.
>
I think there's a philosophy behind replica that suggests humans
are involved therefore there's scope for some fuzzy logic. I'm
not even arguing the merits thereof, it's a perfectly good approach.
What I prefer, however, is the solidity of the dump and a tool to
extract the updates list in a format that makes it possible to
revert them and/or apply them elsewhere.
I'd better be careful, however, I'm beginning to recognise signs
that my attraction for CVS is coming through.
> having mentioned SHA1: there might be an interesting variant that uses
> venti scores.
I won't try to follow your thinking there, it's way beyond my
processing powers :-)
++L
next prev parent reply other threads:[~2004-02-10 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 16:10 Charles Forsyth
2004-02-10 17:24 ` Lucio De Re [this message]
2004-02-11 19:08 ` [9fans] to andrey rog
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 15:49 [9fans] silly replica question (repeated m msgs won't go away) Axel Belinfante
2003-12-02 16:10 ` mirtchov
2004-02-10 3:46 ` Adrian Tritschler
2004-02-10 5:07 ` Geoff Collyer
2004-02-10 5:12 ` Lucio De Re
2004-02-10 12:22 ` Charles Forsyth
2004-02-10 12:38 ` Lucio De Re
2004-02-10 15:00 ` David Presotto
2004-02-10 15:08 ` Fco.J.Ballesteros
2004-02-10 15:28 ` Lucio De Re
2004-02-11 1:52 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040210192404.T17981@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).