Re: lang and conf synthesis

> For a dynamic site (where actions will have to be made for each 
> request) this means that on each page we'll have from dozens to 
> hundred of queries to read strings. Far from efficient probably. In my 
> opinion it's wasting server resources. Why read the strings on each 
> page generation while strings will change very slowly ?

The idea is that we design the system such that intelligent caching of 
output is used to avoid actually running any serious code unless 
absolutely necessary.

However after reading your whole message I'm not _as_ biased against 
precaching php files with lang strings "ripped" into them. Basically we 
would phing-build at runtime as files are included instead of doing it 
explicitly before runtime.

> When we envisaged droping phing, I was told caching would replace 
> phinging for strings and that no overhead was to be expected. If 
> there's no caching for php+strings replaced we'll loose a big 
> advantage of bc imo.

There would be caching! ?

> So why don't you want to have php files built at runtime wheread you 
> were ok when they were built by phing ?

hehe, good point...

_a