From: Stefan Beller <email@example.com> To: Eric Wong <firstname.lastname@example.org>, git <email@example.com>, firstname.lastname@example.org Subject: Re: "IMAP IDLE"-like long-polling "git fetch" Date: Wed, 9 Jan 2019 14:27:25 -0800 Message-ID: <CAGZ79kb9Tbnxe1mSnxpqT_FO6Gdi6wxd-r2YarHXRF1sVRyxLA@mail.gmail.com> (raw) In-Reply-To: <20181229043858.GA28509@pure.paranoia.local> On Fri, Dec 28, 2018 at 8:39 PM Konstantin Ryabitsev <email@example.com> 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 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.
next prev parent reply index Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> 2018-12-29 3:56 ` Eric Wong 2018-12-29 4:38 ` Konstantin Ryabitsev 2018-12-29 6:13 ` Eric Wong 2019-01-09 22:27 ` Stefan Beller [this message] 2019-01-09 22:49 ` Konstantin Ryabitsev
Reply instructions: You may reply publically 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: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAGZ79kb9Tbnxe1mSnxpqT_FO6Gdi6wxd-r2YarHXRF1sVRyxLA@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
email@example.com list mirror (unofficial, one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox