Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #28514
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed1.swip.net!news.astraweb.com!border5.a.newsrouter.astraweb.com!border2.nntp.ams.giganews.com!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail |
|---|---|
| NNTP-Posting-Date | Sat, 17 May 2014 05:01:43 -0500 |
| From | "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> |
| Newsgroups | comp.lang.java.programmer |
| References | <l129n9ljlib23qolbsqv4od65ltfjbcghi@4ax.com><ll38ml$rcr$1@dont-email.me> <l9kbn9pa17oi8nod7c0g2erq7766ooavl4@4ax.com> <ll4pd4$o1i$1@speranza.aioe.org> |
| Subject | Re: invalidating caches |
| Date | Sat, 17 May 2014 11:06:36 +0100 |
| X-Priority | 3 |
| X-MSMail-Priority | Normal |
| X-Newsreader | Microsoft Outlook Express 6.00.2900.5512 |
| X-RFC2646 | Format=Flowed; Original |
| X-MimeOLE | Produced By Microsoft MimeOLE V6.00.2900.5512 |
| Message-ID | <meCdnVPfoKIarurOnZ2dnUVZ8h4AAAAA@bt.com> (permalink) |
| Lines | 24 |
| X-Usenet-Provider | http://www.giganews.com |
| X-AuthenticatedUsername | NoAuthUser |
| X-Trace | sv3-rRuFDccJInqCWo3SOmyf9FVVyASK+58GDx2EIMwemRI2Zk4Kt3rDCwuiUV04kdlKWgAUwdB988Fj5OV!J7xoB8gjuz78EFaygCbhmBjdnRUC5s8b8DuuwuUO5SRI7RiVTrz0a8nJUCHn93vyycbqLFbsshg= |
| X-Complaints-To | abuse@btinternet.com |
| X-DMCA-Complaints-To | abuse@btinternet.com |
| X-Abuse-and-DMCA-Info | Please be sure to forward a copy of ALL headers |
| X-Abuse-and-DMCA-Info | Otherwise we will be unable to process your complaint properly |
| X-Postfilter | 1.3.40 |
| X-Original-Bytes | 2228 |
| Xref | csiph.com comp.lang.java.programmer:28514 |
Show key headers only | View raw
Sarah Connor wrote:
> > One useful tip I learned from that tutorial is a server can effectively
> > invalidate caches by renaming a document or image. The client will have
> > to fetch afresh even if the original had a long time to live.
>
> That has the nasty side effect of breaking existing bookmarks and links
> though.
But, on the other hand, the link to the old version remains separate from the
link to the "latest" version which can be a good thing.
Nothing to stop a server having several links. One which always redirects to
the latest, and others which point to specific versions. Note that provided
the redirect is done at HTTP level (or equivalent) then the client and
intermediates can still cache correctly.
Or poor man's cache control: have a query parameter in the URL which the server
always ignores, but which code on the client (presumably JavaScript in the
typical case) sets to a fresh value on each fetch.
-- chris
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
invalidating caches Roedy Green <see_website@mindprod.com.invalid> - 2014-05-15 02:26 -0700
Re: invalidating caches leif.roar@invalid.com (Leif Roar Moldskred) - 2014-05-15 04:56 -0500
Re: invalidating caches Jeff Higgins <jeff@invalid.invalid> - 2014-05-15 16:36 -0400
Re: invalidating caches Roedy Green <see_website@mindprod.com.invalid> - 2014-05-16 01:58 -0700
Re: invalidating caches Sarah Connor <s.connor@gmail.invalid> - 2014-05-16 10:31 +0000
Re: invalidating caches "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> - 2014-05-17 11:06 +0100
csiph-web