Re^7: HTML::Template and authenticated sessions

(We might be getting a bit further afield than needs done in this thread, but ...)

Then I'd move all that complex AND logic into Perl where it belongs. There's no reason your security policy should be embedded in your templates!

The security policy shouldn't be; the logic determining what gets displayed where should. That the latter implements a portion of the former is no fault of the templating system - it's a fault of management stupidity, but that's still a reality for too many developers. *cues up "Let My People Go"*

In general, if you think something isn't in Perl, try it out, because it usually is. :-)
"What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"

Comment on Re^7: HTML::Template and authenticated sessions

Replies are listed 'Best First'.
Re^8: HTML::Template and authenticated sessions by samtregar (Abbot) on May 11, 2005 at 22:00 UTC
The security policy shouldn't be; the logic determining what gets displayed where should. I disagree. The template isn't the right place to decided what to display, it's the right place to decide how to display it. This is fundamental MVC theory. it's a fault of management stupidity You may be given retarded, rapidly changing requirements, but that's no excuse for inflicting them on your HTML designers! -sam	[reply]

Replies are listed 'Best First'.

Re^8: HTML::Template and authenticated sessions
by samtregar (Abbot) on May 11, 2005 at 22:00 UTC

The security policy shouldn't be; the logic determining what gets displayed where should.

I disagree. The template isn't the right place to decided what to display, it's the right place to decide how to display it. This is fundamental MVC theory.

it's a fault of management stupidity

You may be given retarded, rapidly changing requirements, but that's no excuse for inflicting them on your HTML designers!

-sam

[reply]