Re: high availability

> I'd suggest putting things in a database. Not used coda directly, > but we tried a similar approach under NT writing info to shared drives, > and the performance wasn't as good as sharing info in a db. > CODA may be vastly different, but SQL makes more sense, imo. Looks like I made a little confusion about this. I was thinking on using CODA for 2 purposes: 1. store ALL the php scripts (since all web servers will have to use the same copy of them) 2. store php data (like php sessions) I understand that the php data can actually be stored on SQL and might be better as you mention, but any idea how reliable will be to use CODA for storing the php scripts itself ? (so I dont have to rsync all servers and to avoid having a master/slave relationship between them) > How large of a system do you anticipate this being? I actually don't know for sure. but what I do know is that we need something scalable in case of success =) Thanks for your comments. Alex Verstraeten Buenos Aires, Argentina