From: "Roberto E. Vargas Caballero" <k0ga@shike2.com>
To: 9front@9front.org
Subject: Re: [9front] Enabling a service
Date: Wed, 8 May 2024 21:46:43 +0200 [thread overview]
Message-ID: <ZjvWowfjIDbvvbMa@simple-cc.openbsd.amsterdam> (raw)
In-Reply-To: <9df183e7-7a94-4d58-9a68-2dbc0e73018f@posixcafe.org>
Hi,
On Wed, May 08, 2024 at 11:10:00AM -0500, Jacob Moody wrote:
> On 5/8/24 10:49, Frank D. Engel, Jr. wrote:
> > How did it work for Venti when there were multiple users?
>
> My understanding of venti is somewhat limited to take my explanation with a grain of salt.
> If you have divergent fossils using the same venti you will get divergent root scores, they
> become two paths that have to be merged manually.
Yes, that is what would happen. Fossil is not designed at all to be a
distributed shared file system. If you back two fossil fs to the same
venti you will have two different fs, no merge, no conflict, no anything.
> No matter how you cut you are going to have to deal with multiple people merging
> their cache in to the single root of truth with potentially latent updates.
> Either you have to serialize all mutations at the source of truth (and at that point
> you are latent bound) or you have to be clever about merging. A lot of ink has been
> spilled about this problem in the scope of web programming (CRDs iirc), perhaps
> that may serve as some inspiration.
I would suggest to take a look to AFS (Andrew File System, that I think had also
an evoultion but I don't remember the name) and how it works, and the implications.
Sometimes you can merge the changes, and other times you have to request
human decisions.
Regards,
next prev parent reply other threads:[~2024-05-08 19:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 11:32 Rocky Hotas
2024-05-06 11:58 ` Alex Musolino
2024-05-06 12:43 ` ori
2024-05-06 15:16 ` Scott Flowers
2024-05-06 15:37 ` sirjofri
2024-05-06 16:32 ` Stanley Lieber
2024-05-06 22:18 ` Rocky Hotas
2024-05-06 22:59 ` ori
2024-05-06 23:00 ` ori
2024-05-07 8:22 ` Rocky Hotas
2024-05-07 8:29 ` Frank D. Engel, Jr.
2024-05-07 9:03 ` Rocky Hotas
2024-05-07 9:14 ` sirjofri
2024-05-07 21:11 ` Shawn Rutledge
2024-05-07 21:35 ` Kurt H Maier
2024-05-07 21:45 ` sirjofri
2024-05-07 21:54 ` sl
2024-05-07 21:58 ` sl
2024-05-07 23:15 ` Lennart Jablonka
2024-05-07 23:16 ` Shawn Rutledge
2024-05-07 23:45 ` Shawn Rutledge
2024-05-08 0:34 ` Kurt H Maier
2024-05-08 0:35 ` sl
2024-05-08 1:05 ` Jacob Moody
2024-05-08 1:24 ` sl
2024-05-08 7:22 ` hiro
2024-05-08 14:04 ` Stanley Lieber
2024-05-08 12:08 ` Stuart Morrow
2024-05-08 16:37 ` Brian Stuart
2024-05-08 20:16 ` hiro
2024-05-08 21:26 ` Stuart Morrow
2024-05-08 21:17 ` Disconnection-tolerant / distributed filesystems (was Re: [9front] Enabling a service) Shawn Rutledge
2024-05-08 14:25 ` [9front] Enabling a service Jacob Moody
2024-05-08 3:41 ` Ori Bernstein
2024-05-08 4:09 ` sl
2024-05-08 8:39 ` Frank D. Engel, Jr.
2024-05-08 14:17 ` Jacob Moody
2024-05-08 15:49 ` Frank D. Engel, Jr.
2024-05-08 16:10 ` Jacob Moody
2024-05-08 16:33 ` Frank D. Engel, Jr.
2024-05-08 17:27 ` Jacob Moody
2024-05-08 18:00 ` Steve Simon
2024-05-08 19:46 ` hiro
2024-05-08 19:46 ` Roberto E. Vargas Caballero [this message]
2024-05-08 20:34 ` tlaronde
2024-05-08 14:57 ` Lucas Francesco
2024-05-08 15:10 ` an2qzavok
2024-05-08 2:11 ` Thaddeus Woskowiak
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=ZjvWowfjIDbvvbMa@simple-cc.openbsd.amsterdam \
--to=k0ga@shike2.com \
--cc=9front@9front.org \
/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).