The ultimate point, I think, is the caching of the templates in memory. As for storage ... access from multiple servers certainly is an issue. I can think of reasons for or against it, but until I've benchmarked a few solutions in a serious environment (few million hits a day) I don't want to out-guess them.

Either way, you don't have to sell me on the inconveniences of the system. Nearly every design decision in Slash is sacrificing something, often ease of use or development, in the name of speed or security. Not the way I would do it at all. A couple extra web server machines are a lot cheaper than developer time in the long run.

In reply to Re: Re: Re: Re: Where to keep HTML templates for a web application? by legLess
in thread Where to keep HTML templates for a web application? by legLess

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.