* More efficient Atom feeds for public-inbox
@ 2022-04-26 20:53 Leah Neukirchen
2022-04-27 8:31 ` Eric Wong
[not found] ` <20220426224123.GB30933@dcvr>
0 siblings, 2 replies; 3+ messages in thread
From: Leah Neukirchen @ 2022-04-26 20:53 UTC (permalink / raw)
To: meta
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?
thx,
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: More efficient Atom feeds for public-inbox
2022-04-26 20:53 More efficient Atom feeds for public-inbox Leah Neukirchen
@ 2022-04-27 8:31 ` Eric Wong
[not found] ` <20220426224123.GB30933@dcvr>
1 sibling, 0 replies; 3+ messages in thread
From: Eric Wong @ 2022-04-27 8:31 UTC (permalink / raw)
To: Leah Neukirchen; +Cc: meta
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)
^ permalink raw reply [flat|nested] 3+ messages in thread[parent not found: <20220426224123.GB30933@dcvr>]
* Re: More efficient Atom feeds for public-inbox
[not found] ` <20220426224123.GB30933@dcvr>
@ 2022-04-28 17:46 ` Leah Neukirchen
0 siblings, 0 replies; 3+ messages in thread
From: Leah Neukirchen @ 2022-04-28 17:46 UTC (permalink / raw)
To: Eric Wong; +Cc: meta
Eric Wong <e@80x24.org> writes:
> 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 keep forgetting this :x
> I think some of the streaming stuff needs to be updated...
> Would you happen to know if Last-Modified or ETag is more commonly
> supported by clients? ETag may actually be easier *shrug*
I don't know, but I guess most serious software supports both, so just
having ETag should be fine too.
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-04-28 17:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-26 20:53 More efficient Atom feeds for public-inbox Leah Neukirchen
2022-04-27 8:31 ` Eric Wong
[not found] ` <20220426224123.GB30933@dcvr>
2022-04-28 17:46 ` Leah Neukirchen
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).