--=-77nuA6DYndv2sWpxJ2oD
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
> On the cheap side, CODA sounds promising. Can it reconnect &=20
> re-authenticate to the warm-standby server?
CODA doesn't work quite like that, think of the servers more as peers
that all cache each other's data. The clients also exist in this kind
of persistent caching mode. So basically, if a server goes down, the
data will be cached somewhere (you can force this, it's not entirely
random, although, you could do that too). So basically the 'server
pool' will have the data. So basically with each server a certain
amount of storage is dedicated to 'usable' space, and a part of it is to
cache. I'm sure that there is some sort of tuning that goes on there
with experience :)
You've pretty much exhausted all of my CODA knowledge, I've only set up
one server and one client at home, and read the architecture
documentation. I'm sure that if wanted to know more about 'large
systems' you could e-mail the list. I'm pretty sure that CS at CMU is
using CODA.
Have fun,
Ted
--=-77nuA6DYndv2sWpxJ2oD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see
http://www.gnupg.org
iEYEABECAAYFAj2jzKgACgkQLE335pRPGp38wACgt+qExpZtsU1AjoRlYWOBeiAO
Wz4AoMNAfeVna1hT0hA6Kl0h0S40gCMJ
=Qit9
-----END PGP SIGNATURE-----
--=-77nuA6DYndv2sWpxJ2oD--
(text/plain)