You are going to litter your templates with a huge number of <TMPL_IF CONFIG_FOO_1> type statements.
And? You need conditional behavior, you use a tmpl_if. I don't see a problem here.
If you associate more than two objects, collisions are a very real possibility, especially if you associate your $cgi and $config objects at the same time.
So use one of the other two solutions I presented, or don't associate your query object. I don't do that much anymore personally - it's too hard to police.
The alternative that TT provides is a method-like invocation on your objects.
So you like your syntactic sugar. I get it. What does this have to do with session handling?
Plus, you have run-time includes, which H::T (AFAIK) does not support.
If you can't figure out how to do this with HTML::Template's filter option then you need to try a little harder!
-sam
PS: When do you want me to break out the benchmarks? You know they're coming!
In reply to Re^4: HTML::Template and authenticated sessions
by samtregar
in thread HTML::Template and authenticated sessions
by ghettofinger
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |