The computational burden of frying varies greatly depending on the amount of
processing is performed on a per request basis. For instance, a page that
that is build like this is pretty lightweight:
<HTML>
<HEAD>
<TITLE>
Server Side Includes
</TITLE>
</HEAD>
<BODY>
<!--#include virtual="/navbars/header.html" -->
Standard headers and footers are a piece of cake with SSI's
<!--#include virtual="/navbars/footer.html" -->
</BODY>
</HTML>
This case would use the mod_include semantics to build the final
presentation with header and footer components. There's no computation
going on beyond employing Apache's subrequest mechanism to resolve the
request for virtual documents. However, the basic idea here on which we'll
benefit from architecturally (even if we're using something more sophisticated
than SSI's) is that the page is built of fry-time components.
