Thank you Ivan,

	The frontend servers will not have the same content. So even if
user upload files through then, it will be no problem. The big
opperation here will be the reading.

	Coda has some space storage limitations? I was going to install
it in a machine with RAID 5 (5 discs with 18G each) wich gives me 72G of
storage space. Coda can't handle it? 

Thanks
Thiago Lima.

	 

-----Original Message-----
From: Ivan Popov [mailto:pin_at_math.chalmers.se] 
Sent: Wednesday, November 06, 2002 4:40 AM
To: Thiago Madeira de Lima
Cc: codalist_at_TELEMANN.coda.cs.cmu.edu
Subject: Re: FW: Coda in a web hosting environment


Hello,

>     I'm setting up a webserver farm with 3 machines. 2 will be 
> frontends with apache and one will be the storage server.
>
>     I was thinking about using NFS to do that, but maybe CODA will be 
> a better solution?

it depends on your needs. NFS is surely easier to set up,
Coda has some limitations on storage space and implements no locking
(you may need it in case you are going to modify data via the web
interface).

You will face the need for either not using Coda access control at all
(pity?) or cache Coda tokens at the web server and arrange "personality
switching" depending on the users' authenticity. Quite doable of course.

In case you modify data from the webservers, as you have more than one
server, you users can create conflicting updates (and be effectively
locked out of the system until a manual intervention) - unless you
prevent it by some other means, say by implementing locking on
CGI-script level.

Otherwise if your data is "readonly", you should be pretty safe with
Coda and enjoy its caching and server failure resilience.

Regards,
--
Ivan