This depends on how much work you want the template to do. It's one thing to create a session and provide it to the template. It's another to have the template do all the work.

FWIW, I tend strongly toward the first option. Decoupling the display of the data and the manipulation of the data will pay off in the long run. (perrin always has good arguments about this on the relevant mailing lists)

That said, the Apache::Template module is very straightforward and encourages this sort of action, since it's template-driven rather than code driven. Creating a session plugin would be fairly simple and wouldn't seem to affect much else. So I'd say go ahead and create it -- since it's independent it shouldn't be too much trouble to replace it later if you find it doesn't meet your needs.

Chris
M-x auto-bs-mode


In reply to Re: Template::Toolkit::Session by lachoy
in thread Template::Toolkit::Session by mitd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.