danieljean
msg:589083 | 2:11 am on Mar 27, 2004 (gmt 0) |
If the new newsletter doesn't have the same file name, you don't have the caching problem. You'll just need to update the link to the latest newsletter so it's always linking to the latest issue.
|
dcrombie
msg:589084 | 10:54 am on Mar 27, 2004 (gmt 0) |
Instead of changing the filename, you can add a timestamp to the newsletter link. eg. <A href="newsletter.pdf?20040326">Newsletter</A>
|
nafmo
msg:589085 | 12:55 pm on Mar 27, 2004 (gmt 0) |
If you post your newsletter on a specific time, you should probably add an Expires header so that the old one isn't valid when the next is published.
|
mikegram
msg:589086 | 4:52 pm on Mar 27, 2004 (gmt 0) |
Daniel, changing the filename would be a simple and effective solution. I'm told that new files require some extra steps by our server admin to make them publicly accessible. A small point, but I'm hoping to avoid creating extra work for anyone else. Dcrobie, what exactly would be the effect of the timestamp and is this solution server specific? Nafmo, where would I put this and what does the syntax look like? Thanks very much for all the ideas.
|
g1smd
msg:589087 | 9:23 pm on Mar 28, 2004 (gmt 0) |
Oooh. As a user I would be annoyed if every edition was called newsletter.pdf each time - I think that you should date them individually: newsletter.2004.03.28.pdf etc, to solve both problems (Use Y-M-D date so that they automatically sort into the correct date order in directory listings).
|
dcrombie
msg:589088 | 11:03 am on Mar 29, 2004 (gmt 0) |
URL's with GET parameters are not cached in most circumstances. Some older browsers cache the file including the GET parameters but by using 'YYYYMMDD' each day you get around that as well.
|
danieljean
msg:589089 | 2:17 pm on Mar 29, 2004 (gmt 0) |
>Daniel, changing the filename would be a simple and effective solution. Exactly. I'm a lazy programmer (as all good ones ought to be), and that's the easiest solution by far. If the admin is remotely competent, have them make a /newsletter directory that is publicly accessible. If you are causing them less work than you save yourself, you shouldn't feel bad. Using the naming convention that g1smd suggested would be great, both for yourself and users. Also, if you have access to even a light scripting language, you should be able to have the newsletters page automatically update as soon as you upload the newsletter.
|
|
