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: AS15169 209.85.128.0/17 X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 4AF261F4D8 for ; Thu, 28 Apr 2022 17:46:49 +0000 (UTC) Received: by mail-ej1-f49.google.com with SMTP id i27so11017809ejd.9 for ; Thu, 28 Apr 2022 10:46:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=cpcumydlqXHfiSFhSGoH3onSbAzXE31BsyVQgk8F8Y0=; b=vBKlk8D1ieW/D5+IIFa+DoVvlddAtV96YL0Hn+35vw2KVQKfPEMiIXelVm94wQM9wb UXkUSrz3v3udzoiL6i9CT5ke2Rn7VJ/jir8PvrlLSuwdX/J9J1rZ8ViZBK0IYCa430TM fozotDEgk+fi3syRVPMM3ezkERhWRJuR6r08LV+9kNCYAQkhwIxMrKiC9MysC8ZjmKpy cLS/YJgWVZDibZj9yzPHMxVmy5GIxrJU20Pl10u/lkC1UfNfJRqdAZNmnCS4VSiCFnBF CT/jgtBIuUoX2WpYx/aRZd9NKcMiWU5g2HoE7mYlzdncGtd7fhbBXXV25R0uzM33Ja8I 0NyA== X-Gm-Message-State: AOAM532834gCJA+9FRpidBxZDYJkwLW1cJpTiOKQrKkQR1OaPKzcCuhc f0pdcXKSW9TkyKGk5tLMLbo= X-Google-Smtp-Source: ABdhPJzEd/1itz2gNr408AFgr6W5s40CvMKIIzB+uOXHv3Vra2BJsyv5La/jaIjjBp01DO5KSjkBFg== X-Received: by 2002:a17:906:1e94:b0:6cc:4382:f12e with SMTP id e20-20020a1709061e9400b006cc4382f12emr32180128ejj.482.1651168007432; Thu, 28 Apr 2022 10:46:47 -0700 (PDT) Received: from rhea.home.vuxu.org (rhea.home.vuxu.org. [2a0e:46c4:2400:1ea4:ea6a:64ff:fe4d:ff9e]) by smtp.gmail.com with ESMTPSA id w24-20020a056402129800b0042617ba6388sm1907911edv.18.2022.04.28.10.46.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Apr 2022 10:46:46 -0700 (PDT) Received: from localhost (rhea.home.vuxu.org [local]) by rhea.home.vuxu.org (OpenSMTPD) with ESMTPA id 3dfccd61; Thu, 28 Apr 2022 17:46:45 +0000 (UTC) From: Leah Neukirchen To: Eric Wong Cc: meta@public-inbox.org Subject: Re: More efficient Atom feeds for public-inbox In-Reply-To: <20220426224123.GB30933@dcvr> (Eric Wong's message of "Tue, 26 Apr 2022 22:41:23 +0000") References: <87pml3ftx1.fsf@vuxu.org> <20220426224123.GB30933@dcvr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) Date: Thu, 28 Apr 2022 19:46:45 +0200 Message-ID: <877d79f6d6.fsf@vuxu.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: Eric Wong writes: > 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 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 https://leahneukirchen.org