[tahoe-dev] split brain/partition tolerance? how handled in tahoe -- docs?

[Tony Arcieri]

On Wed, Aug 8, 2012 at 10:56 AM, Two Spirit <twospirit6905 at gmail.com> wrote:

> To respond to an earlier post on this thread, I see a few scenarios, but
> other scenario's that I'm thinking of is the source control repository
> (don't even want to ask about database support yet). If the source control
> repository was inside of Tahoe, inconsistency on a merge, can't even start
> to figure out how much work is involved in recoverying 100% from that.
>

Why would you store source control repositories or databases that are
actively being modified by multiple participants inside of Tahoe? Both of
these things are designed to be network services that you interact with
over a sockets layer, as opposed to coupling through a filesystem.

-- 
Tony Arcieri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120808/5704aea1/attachment.html>