From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server speed
Date: Thu, 17 Jul 2014 12:01:29 -0700 [thread overview]
Message-ID: <20140717190129.81607B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 17 Jul 2014 11:14:01 PDT." <33E5CFC9-B6F3-49F4-90F6-2674A96745CE@bitblocks.com>
On Thu, 17 Jul 2014 11:14:01 PDT Bakul Shah <bakul@bitblocks.com> wrote:
>
> On Jul 17, 2014, at 9:56 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > i would think the same approach would work with fossil. of course one
> > would need a more sophisticated solution than "just wait forever", due to
> > the tcp connection.
>
> There is no particular reason for it to be tcp given lack of any
> authentication. The beauty of CAS is that it need not even talk
> to the same server!
To expand this a bit:
So long as a server returns a block corresponding to its SHA1
score, you (the client) don't care whether it is the same
server you wrote the original block to or another (and you can
always verify the returned block). This opens up some
interesting choices. For instance, you can multicast each read
or write or you can set up a hierarchy of servers and switch
to another one (or even get different blocks from different
instances). How the writes are handled/replicated.stored is
entirely upto the server (cluster). Or you can implement a
bittorrent like facility on top of venti (I call it bitventi
or b20).
I have been playing with Lucho's 'govt' package to explore
stuff like this (though staying with the current venti wire
protocol for now).
next prev parent reply other threads:[~2014-07-17 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 6:13 kokamoto
2014-07-15 13:02 ` Anthony Sorace
2014-07-15 16:30 ` cinap_lenrek
2014-07-15 16:56 ` erik quanstrom
2014-07-16 0:04 ` kokamoto
2014-07-16 0:36 ` kokamoto
2014-07-16 17:26 ` erik quanstrom
2014-07-16 14:23 ` Steven Stallion
2014-07-16 14:53 ` Ramakrishnan Muthukrishnan
2014-07-17 1:13 ` Steven Stallion
2014-07-17 17:13 ` Ramakrishnan Muthukrishnan
2014-07-17 21:44 ` cam
2014-07-16 17:41 ` erik quanstrom
2014-07-16 23:15 ` kokamoto
2014-07-17 0:29 ` Steven Stallion
2014-07-17 0:31 ` Steven Stallion
2014-07-17 1:10 ` john francis lee
2014-07-17 1:09 ` john francis lee
2014-07-17 1:10 ` Bakul Shah
2014-07-17 16:56 ` erik quanstrom
2014-07-17 18:14 ` Bakul Shah
2014-07-17 18:39 ` erik quanstrom
2014-07-17 19:01 ` Bakul Shah [this message]
2014-07-17 19:10 ` erik quanstrom
2014-07-17 19:26 ` Bakul Shah
2014-07-16 17:23 ` erik quanstrom
2014-07-16 23:01 ` kokamoto
2014-07-17 17:03 ` erik quanstrom
2014-07-18 16:50 ` hiro
2014-07-18 19:36 ` erik quanstrom
2014-07-18 20:11 ` Bakul Shah
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=20140717190129.81607B827@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/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).