[tahoe-dev] Can Tahoe works well in this scenario?

[Greg Troxel]

For your use case tahoe is not yet baked enough.
It's also possible tahoe is not the right tool for your problem.
Also check out coda:
  http://www.coda.cs.cmu.edu/

tahoe doesn't currently have servers do resyncing automatically.  That's
done by clients running repair.

You might want to decouple the concept of client nodes and servers, even
though by default a server is a client.

  In my deployment, I would consider it is not acceptable that a1 can only be
  accessed from A WUI because all my 3 servers are running in the different
  places in the world behind their own firewalls. Accessing a file from remote
  server from WUI is not acceptable and against the original security design
  of Tahoe project.

Your clients all need to be able to connect to all servers.  You'll have
to fix the firewall :-)

share placement is not particularly well controlled, and in the tahoe
vision is not super important - you have many servers and put shares on
a number of them.

I think you could change tahoe's code to do what you want; with 1/1/3
sharing you can upload to 1 server (not having any redundancy) and then
repair should try to copy to more servers as it is able.  While 1/1/3
would be viewed as odd by most, 2/4/7 might be more normal and would
still benefit from improved share placement and repair code.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20101202/b20341ce/attachment.pgp>