On Sun, 27 May 2007 16:44:53 -0600, M. David Peterson
<m(_dot_)david(_at_)xmlhacker(_dot_)com> wrote:
taking *FULL* advantage of browser caching to ensure only the views and
data sources and their respective mappings/bindings necessary to build
out each page are accessed at runtime.
That made no sense. Browser caching ensures that each view can be cached
after its first access, requiring access to only the data necessary to
build out each new page that calls upon that view. The underlying XSLT
code itself ensures only the files necessary to build out each page are
accessed at runtime, the browsers cache ensures it does so in the most
efficient manner.
--
/M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |
http://dev.aol.com/blog/3155
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--