Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Sarah Connor <s.connor@gmail.invalid>
Newsgroups: comp.lang.java.programmer
Subject: Re: invalidating caches
Date: Fri, 16 May 2014 10:31:00 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 8
Message-ID: <ll4pd4$o1i$1@speranza.aioe.org>
References: <l129n9ljlib23qolbsqv4od65ltfjbcghi@4ax.com> <ll38ml$rcr$1@dont-email.me> <l9kbn9pa17oi8nod7c0g2erq7766ooavl4@4ax.com>
NNTP-Posting-Host: /Y8o+/kzUMV/8RkTMAAXJA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: slrn/3.1 (USERIX 1.7)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:28493

On Fri, 16 May 2014 01:58:32 -0700, Roedy Green 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.