Are you expecting it to be used by nodes that cross an administrative
boundary?


Zooko O'Whielacronx wrote:
>> So what's the plan for Tahoe, Zooko? Are you working on getting it
>> bundled with unix distributions? Is your strategy to aim at low-churn
>> servers or high-churn clients?
>
> So, yeah, allmydata.com stopped funding new Tahoe development a few
> months ago [1]. Tahoe, the Longlived Axe-tolerant File System, is now
> a purely volunteer-driven community project. The current version is
> already functional and reliable -- it has been in production use in
> allmydata.com for more than a year, storing all of the allmydata.com
> customer files. Our goals do indeed focus on getting Tahoe included
> in Debian, Fedora, Gentoo, and Ubuntu this summer [2].
>
> I'm not sure I understand your question about churning servers and
> clients. Tahoe is explicitly designed for low-churn servers -- I've
> become increasingly skeptical of the whole notion of relying on
> high-churn servers for reliable long-term storage. They don't have to
> be expensive reliable servers, though -- allmydata.com uses cheap
> commodity servers and other Tahoe deployments use people's home PCs.
>
> The issue of "churn" is irrelevant to Tahoe clients -- nobody else
> relies on other clients so they can come and go as they please.
>
> Thanks for asking!
>
> [1] http://allmydata.org/pipermail/tahoe-dev/2009-March/001461.html #
> tahoe needs funding! (and Zooko is available for work!)
> [2] http://allmydata.org/pipermail/tahoe-dev/2009-April/001627.html #
> questions about development priorities for Tahoe-LAFS, summer 2009
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>