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=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL shortcircuit=no autolearn=unavailable autolearn_force=no version=3.4.2 Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AF9891F803 for ; Wed, 9 Jan 2019 22:27:38 +0000 (UTC) Received: by mail-ed1-x544.google.com with SMTP id y56so8596901edd.11 for ; Wed, 09 Jan 2019 14:27:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=FndS91tq90stP9O1UEOaOvoWUNCLLXIOJRwldVKS8/g=; b=OX1bMFIRi4Y96N4q0QZ2qpnKApYJod7IWWQsDMueFFUU8AUJIU905+IJrLP9p+RTfI JV5h4bRGcrlvQdHkfdYRoi00kwPEJBFrNf6SBdn+RCIKYozbt3kJe+8XhGcqPWSIcWK1 c2/V58/UV9MnBkaC826SpRzrExZToxRiOYIjT8hm/2/pZLoGUcI3BkC/z4ISWeKxv0Ew 5bwWOHQkvbsvzeXeMkBU0pC3rJa1MyBp8BRRVTSwbSS3yBe6GPVZWQhMfUueJhBRNJf9 Ei7SNggeHrQtfPVQVm9cg0ieWscn80yvkQ2SB3XvoLZksdJC9Fz2i+KjA80mCQoFWMWG eOPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=FndS91tq90stP9O1UEOaOvoWUNCLLXIOJRwldVKS8/g=; b=J8DFSYurFL8hWAbUhbQuxqvdh55812D4Qalp/kX0RKgsFbRx0L8VR7lkwTkQPKP6l5 urRtJYmemlNt5MMxeIuaWYQ3hGAm+fKGIWR9aTVwESGPfpMOwppkA84Kj4i7BREjTbI4 zuZ6Rtu2Rlfpu3LZf66Hp1uxm4EJX11P8F0Fxdbyl2090jcGv4FZUA9UaC/kE+pqTp2z IZVlJU2QDsETGqTeN4jAH2Ty8WTt3xpQfQIYS7exTQeB0esv2gt/soKgWTjI7+igstj9 JNM+x9XIzLhU/x3QDy9RB33qM4G8BU7oRoUzqY6pKYHBfZ0YUfMgxpVcmr0ZpRwUXm+Y FZ3w== X-Gm-Message-State: AJcUukcWJ7ZcUfP99wdComG8t9ksdTVVXIwbgWtwkBu1aBebkkFKI15a AxHKcdrOxkS4qdLqMwxenjI8xfOA++WRNTQxUuPBsQ== X-Google-Smtp-Source: ALg8bN4trEC2ZlAB+5zzEKadcECPLv0+n52n48mR6imbIHXBJLpEn7/2Ysoo3hoIvhV6SCCUsV95rtuAQpsuT++uDhg= X-Received: by 2002:a50:8fe4:: with SMTP id y91mr7397094edy.231.1547072856355; Wed, 09 Jan 2019 14:27:36 -0800 (PST) MIME-Version: 1.0 References: <20181229034342.11543-1-e@80x24.org> <20181229035621.cwjpknctq3rjnlhs@dcvr> <20181229043858.GA28509@pure.paranoia.local> In-Reply-To: <20181229043858.GA28509@pure.paranoia.local> From: Stefan Beller Date: Wed, 9 Jan 2019 14:27:25 -0800 Message-ID: Subject: Re: "IMAP IDLE"-like long-polling "git fetch" To: Eric Wong , git , meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" List-Id: On Fri, Dec 28, 2018 at 8:39 PM Konstantin Ryabitsev wrote: > > On Sat, Dec 29, 2018 at 03:56:21AM +0000, Eric Wong wrote: > > Hey all, I just added this to the TODO file for public-inbox[1] but > > obviously it's intended for git.git (meta@public-inbox cc-ed): > > > > > +* Contribute something like IMAP IDLE for "git fetch". > > > + Inboxes (and any git repos) can be kept up-to-date without > > > + relying on polling. > > > > I would've thought somebody had done this by now, but I guess > > it's dependent on a bunch of things (TLS layer nowadays, maybe > > HTTP/2), so git-daemon support alone wouldn't cut it... > > Polling is not all bad, especially for large repository collections. I disagree with that statement. IIRC, More than half the bandwidth of Googles git servers are used for ls-remote calls (i.e. polling a lot of repos, most of them did *not* change, by build bots which are really eager to try again after a minute). That is why we use a superproject, with all other repositories as a submodule for polling, as that would slash the ls-remote traffic approximately by the number of repositories. There was an attempt in JGit to support this type of communication of long polling at https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/2adc572628f9382ace5fbd791325dc64f7c968d3 but not a whole lot is left over in JGit as it was refactored at least once again. IIRC the issues where in the lack of protocol definition that made it usable for a wider audience.