From: Alex Bochannek <alex@bochannek.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49033@debbugs.gnu.org
Subject: bug#49033: 28.0.50; [PATCH] Feature suggestion, url-cache-expiry-alist to override expire time for cache pruning
Date: Sat, 19 Jun 2021 12:32:13 -0700 [thread overview]
Message-ID: <m2y2b5mz0i.fsf@bochannek.com> (raw)
In-Reply-To: <877diq2gqw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 19 Jun 2021 14:14:47 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Alex Bochannek <alex@bochannek.com> writes:
>
>> Support URL-specific cache expiration
>>
>> * test/lisp/url/url-cache-tests.el: Test URL-to-filename and
>> filename-to-URL mappings used by URL caching.
>>
>> * lisp/url/url-cache.el (url-cache-expiry-alist)
>> (url-cache-create-url-from-file, url-cache-expired)
>> (url-cache-prune-cache): Expire cache entries based on regular
>> expressions matching URLs defined in new customizable variable
>> url-cache-expire-alist.
>>
>> * doc/misc/url.texi (Disk Caching): Mention
>> url-cache-expiry-alist variable.
>
> Looks good to me. What's the use case for this, though?
I originally had looked at this for Gravatar entries and I am now using
it to avoid fetching the same images in RSS feeds. I just noticed though
that `url-cache-create-url-from-file' won't work if
`url-cache-create-filename-human-readable' is used. Any suggestions for
how to address that?
--
Alex.
next prev parent reply other threads:[~2021-06-19 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 5:40 bug#49033: 28.0.50; [PATCH] Feature suggestion, url-cache-expiry-alist to override expire time for cache pruning Alex Bochannek
2021-06-15 14:11 ` Lars Ingebrigtsen
2021-06-15 22:55 ` Alex Bochannek
2021-06-19 12:14 ` Lars Ingebrigtsen
2021-06-19 19:32 ` Alex Bochannek [this message]
2021-06-21 12:21 ` Lars Ingebrigtsen
2021-06-21 18:25 ` Alex Bochannek
2021-10-24 7:27 ` Stefan Kangas
2021-10-27 16:36 ` Alex Bochannek
2021-10-27 16:50 ` Stefan Kangas
2021-06-19 12:56 ` Benjamin Riefenstahl
2021-06-19 19:24 ` Alex Bochannek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y2b5mz0i.fsf@bochannek.com \
--to=alex@bochannek.com \
--cc=49033@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).