Isn't it not enough
1. To write a database connection class (API). I think that class is already written in PEAR, so you do not need to reinvent the wheel. Then you use that class on the different sites. The PEAR connection class ought to (I do not know it in detail) take care of timeouts and server down cases.
2. It is always a good practice to store configuration information in a file and require (include) it in your applications.
3. If it contains sensitive information like passwords etc. the .ini file should be located in a directory that it is difficult to guess the name and location of and give it a cryptic name. If you know the PHP parse_ini_file function, you can parse that sensitive information (CrypiticNameConfiguration.ini file) and in that way make it more hidden to potential hackers.
|