That's interesting. Just curious, is it easy to deploy this in a
web-facing manner? For example, at Expensify we store a bunch of
receipt images. We currently do it with S3, and they're fine, but I'm
always interested in alternatives. If I got a handful of dedicated
servers scattered around the world, all with huge hard drives, could I
easily configure Tahoe in conjunction with a webserver to:

1) Upload a receipt to any server using HTTP PUT

2) Fetch a receipt image from any server using HTTP GET

3) Automatically balance redundant storage such that DNS load balancing
"just works" for both uploads and downloads

Does it do this out of the box by some miracle? If coding is involved,
can you give me a quick overview of the steps I'd need to take?
(standalone C++, lighttpd/PHP, anything is fine.)

Thanks!

-david

Lucas Gonze wrote:
> Zooko O'Whielacronx wrote:
> The two kinds
>> of deployment so far are the allmydata.com use case in which a company
>> operates hundreds of servers and customers pay a monthly fee to get
>> access, and the friendnet (what Ian Clarke named "darknet") use case,
>> where a group of friends all let each other use their computers out of
>> love.
>
> This makes me think of a hybrid model where there's a coop of businesses
> or sophisticated friends. Maybe 5-100 companies.
>
> What's the latency like? How does it feel on an application level to
> use this instead of a typical SAN?
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>