In terms of memory, I was thinking more along the lines of how much
memory the HTML::Template and Text::TagTemplate modules take up
themselves.
I want all of my templates in the apache process - they're going to be
reused constantly and if they need to be changed i have no problem
doing a graceful restart.
There's a 40k difference between the two .tar.gz distributions. I
don't know what that will turn into when run - i'm sure 80% of either
of those is POD documentation. A 20k difference on my current setup
should get me 2 more apache children though - which is a bit of a plus.
I don't want to develop anything to handle this simple thing either...
but this is just one part of something more complex that I'm pretty
sure SSI will not work with.
Thanks for all of your pointers though - as always they're incredibly
valuable.
On Aug 12, 2005, at 4:16 PM, Perrin Harkins wrote:
On Fri, 2005-08-12 at 16:07 -0400, Jonathan Vanasco wrote:
This looks useful as well. I think i might bench HTML::Template and
Text::TagTemplate against one another for memory usage.
HTML::Template can store the parsed templates on disk outside of the
apache process. Check the section on caching options.
If/else and loops are already 'too much' -- I essentially just want
variable substitution.
I wouldn't want to try to develop anything without the ability to do
includes, loops, and boolean IFs, but you can try. SSI really is a
viable solution for this, and doesn't store anything in memory.
- Perrin
