From: Eric Wong <e@80x24.org>
To: Leah Neukirchen <leah@vuxu.org>
Cc: meta@public-inbox.org
Subject: Re: More efficient Atom feeds for public-inbox
Date: Wed, 27 Apr 2022 08:31:39 +0000 [thread overview]
Message-ID: <20220427083139.M723659@dcvr> (raw)
In-Reply-To: <87pml3ftx1.fsf@vuxu.org>
Leah Neukirchen <leah@vuxu.org> wrote:
> Hi,
>
> currently, public-inbox sends the Atom feed with
> Content-Type: application/atom+xml and no further headers.
>
> Since many feed readers poll feeds quite often, this creates noticable
> traffic and load.
>
> Would it make sense to serve the <updated>...</updated> field as
> Last-Modified and/or compute some ETag, so feed readers can use
> conditional GET?
Yes, thanks for the reminder. I think some updates to the
streaming code needs to be made.
Btw, would you happen to know if ETag or Last-Modified support
is more common amongst common feed reader clients?
(btw, I thought I replied to this email many hours ago, but
I don't think it went out before I lost power :x)
next prev parent reply other threads:[~2022-04-27 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 20:53 More efficient Atom feeds for public-inbox Leah Neukirchen
2022-04-27 8:31 ` Eric Wong [this message]
[not found] ` <20220426224123.GB30933@dcvr>
2022-04-28 17:46 ` Leah Neukirchen
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220427083139.M723659@dcvr \
--to=e@80x24.org \
--cc=leah@vuxu.org \
--cc=meta@public-inbox.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.
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).