From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id B19D31F4D7; Wed, 27 Apr 2022 08:31:39 +0000 (UTC) Date: Wed, 27 Apr 2022 08:31:39 +0000 From: Eric Wong To: Leah Neukirchen Cc: meta@public-inbox.org Subject: Re: More efficient Atom feeds for public-inbox Message-ID: <20220427083139.M723659@dcvr> References: <87pml3ftx1.fsf@vuxu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87pml3ftx1.fsf@vuxu.org> List-Id: Leah Neukirchen 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 ... 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)