|
Monday 05 January 2004 9:20:08 am
This has been brought up in the past, but I thought I would post again to see if anyone else has addressed the issue or at the least begun thinking about it. It would be really helpful to both the developers and the users of their sites if we had a safe way to establish a last-modified date, or an e-tag to pages generated by the system. Either of these options would allow developers to set up their site to cache pages on the user's machine, or a cache-server to speed up the site's response.
[Last-Modified]
The problem we have run into when using Last-Modified dates is the fact that the only date that can be pulled is that of the page's content modification which isn't changed when an item that is fetched has changed. So, if you change an item in the site's navigation, all of the pages that had not been modified recently would break.
[E-Tags]
E-Tags look like a promising alternative for us as they provide the ability to simply compare byte-count between two pages. I have not had a chance to extensively test these out, but I hope e-tags will allow us to avoid the problems stated above under Last-Modified. Has anyone else worked with either of these methods? If so, I would appreciate hearing about your experiences! Alex
Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]
<i>When in doubt, clear the cache.</i>
|
