vbox4php-develop

[Philipp <phi...@gm...>]

Okay,

here is a small disadvantage of the CVS work. It's the config stuff.

Currently you will find in CVS the file vboxconf.php3. This stores all the 
global definition and the configuration.
As for the last weeks, this has been easy for me, as I was able to place my 
local configuration even into the CVS, but when we want to work on one 
vbox4php together I assume that we have different configuration habbits (at 
least the IPs for the vboxd will be different).

Therefore we need a different approach within CVS:
I think, as the class cvboxConf already has an Init-Function, we use this 
Init-Function to parse a local Text-Configfile. This Text-Configfile does 
contain the individual configuration and is not synced with all the 
CVS-commits/updates.
This has the disadvantage that on every access to the vbox4php site, this 
file must be parsed, which is much slower than with predefined configs.

On the other hand, for each release we can skip this local parsing and place 
all the configuration into the vboxConf directly.

Or we define an include to the individual settings as a php-config, but then 
on each new configuration item, you need to add this manually.

Hopefully I made the problem clear.

What do you think about this approach? Do you have another idea/suggestion?

Philipp