From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti workalike in Python
Date: Thu, 11 Dec 2003 11:23:48 -0500 [thread overview]
Message-ID: <E1AUTbQ-0000em-8I@t40.swtch.com> (raw)
In-Reply-To: Your message of "Thu, 11 Dec 2003 09:46:02 GMT." <gAUBb.655572$pl3.322652@pd7tw3no>
> > > Having said that, is there any documentation on the venti protocol apart
> > > from the source?
> >
> > Not really, but here's a summary.
> >
> > Venti uses a simple RPC protocol with only a few messages:
> > ...
>
> Many thanks.
>
> > size[2] QSync tag[1]
> > size[2] RSync tag[1]
>
> These aren't in the source I have. Presumably they were added relatively
> recently. I assume they mean save all transactions to disk?
I added them about a year ago. Sync means "don't return until everything
I've sent up to this point is committed to disk".
Russ
next prev parent reply other threads:[~2003-12-11 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 2:00 John E. Barham
2003-12-10 2:31 ` Russ Cox
2003-12-10 2:51 ` Geoff Collyer
2003-12-10 22:52 ` William Josephson
2003-12-11 7:20 ` John E. Barham
2003-12-11 9:46 ` John E. Barham
2003-12-11 16:23 ` Russ Cox [this message]
2003-12-10 12:11 Geoff Collyer
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=E1AUTbQ-0000em-8I@t40.swtch.com \
--to=rsc@swtch.com \
--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).