- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Sat, 19 Jan 2002 14:05:06 +0000 (GMT)
- To: w3c-wai-ig@w3.org
> Why? How a developer decides to manage their content is entirely up to > them, it should have no bearing on the result sent to the client - now you > could say that server parsed HTML for static pages is often misused so as > to break caching of the page - but that doesn't invalidate server parsing > itself, and static pages are also often broken as regards to caching. It tends to be easy for a user to add got to server parsed HTML to add some small gimmick or even to avoid repeating the same menu on each page, but it takes a rather sophisticated user, and suitable tools, to do that and maintain cachability. You are correct that the reason I made this comment is cachability, but shtml seems to be so attractive to people and cachability so little appreciated, that the simple rule is to avoid server parsed HTML, even when the real rule is to make the pages as cachable as the application will bear. Truly static pages get cachability by default but shtml and CGI pages require positive effort.
Received on Saturday, 19 January 2002 09:05:10 UTC