Perrin,
you mean that I can actually set my environment per virtual-host?
that's encouraging in the one-implementation per site scenario. Now I
does block any use of persistent variables, unless I store them in a
RDBMS or in the 'Globals' module you mentioned. It could really be a
module that just exported references to internal hashes. I'm starting to
like it.
A module that exported persistent hashes (not across server restarts,
just across requests ... short lived persistence). Maybe it could be
loading the 'config' hashes from disk every once in a while, say every
10 seconds, to be able to reconfig without restarting. And the ability
to commit a given hash ('config') to disk to make it permanent.
mmmh. an idea is shaping here in my tiny head ... anyone care to
comment?
martin
Perrin Harkins wrote:
>
> You can have a module full of globals that is different for each site (it
> doesn't have to go in the same directory as your other shared code), or
> you can put things in httpd.conf with PerlSetVar and read them with
> $r->dir_config(), which allows a separate configuration for each virtual
> host.
>
> - Perrin
