* Dave Hodgkinson <[EMAIL PROTECTED]> [2002-06-07 07:41]:
> Andy Wardley <[EMAIL PROTECTED]> writes:
>
> > then you should get 3 different template objects, one for the outer
> > context, another for foo which merges the outer and inner configs,
> > and another for bar which does the same.
>
> For me, the killer is that it fails outside completely different
> servers. I'm currently running five single threaded backend
> Apache::Template servers!
My solution to this (I have written and am using a different module
which does basically the same thing as Apache::Template) was to have a
separate Service instance for each virtual host, and to just be careful
about not defining nested configuration directives that get processed at
runtime.
The real solution to this is to make every element of TT that can be
controlled by a configuration parameter be modifiable by a mutator
method, and, at the beginning of each request, modify the appropriate
aspects of the Template objects.
(darren)
--
If you pick up a starving dog and make him prosperous, he will not
bite you. This is the principal difference between a dog and a man.
-- Mark Twain
