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
hi list,
i'm about to start writing the first of a series of internal modules,
aimed at handling common features among sites we develop. Like, let's
say, a 'latest news' box or a product guide/database.
Now, the idea is to have one codebase, written in a module that serves
all
On Mon, 24 Jul 2000, martin langhoff wrote:
Now, the idea is to have one codebase, written in a module that serves
all of our sites. Each site should have its own (rather complex)
config. Each and every subroutine must know in which context it's
being called, and I don't really want to pass
