[tahoe-dev] Tahoe as glue filesystem

[Valentino Volonghi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,
	I'm using Twisted Matrix to write a process pool (Ampoule on  
launchpad).
One of the things I'd like to achieve is the possibility to run  
processes on remote
machines and of course here comes the problem of letting them talk to  
each other.

Since one the most interesting uses of these distributed architectures  
is being able
to run mapreduce-kind stuff I was wondering if:

a) does tahoe make any sense for this kind of usage? Seeing that it  
has very strong
read performance my impression is that it does, it might not be  
tailored for this if
subprocesses write too much in it.

b) is it possible to disable parts of the protocol for speed reasons?  
I'm sure that all
or most of the features inside tahoe are extremely useful when storing  
sensible data
or third party data. But this is not true for subprocesses.  
Essentially something very
transparent and that could be inspected would be great (so basically  
limiting capabilities
and encryption a bit or any other feature for different cases).

c) would it be a bad idea to add a 'temporary storage' in tahoe that  
would simply keep
data sent in memory (and distribute it between all introducer's  
clients) in order to be
able to access it from inside this cluster of servers.

Basically I think I see some potential for tahoe to compete against  
hbase and similar
distributed and failsafe filesystems, and I would like to know if  
that's impossible to
obtain or if it requires countless hours and deaths.

thanks

- --
Valentino Volonghi aka Dialtone
Now running MacOS X 10.5
Home Page: http://www.twisted.it
http://www.adroll.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgyAfUACgkQ9Llz28widGUUegCgmxeibKYND7nAj9wxAgnCRn/E
MeMAoIpz6IPDjmWDeQaSwxPWYLIH345r
=W3NK
-----END PGP SIGNATURE-----