Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: is there a possibility for gnus to download data without blocking?
Date: Fri, 21 Aug 2020 10:42:41 -0700	[thread overview]
Message-ID: <871rjzvqsu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v9hc1e92.fsf@dick>

dick.r.chiang@gmail.com writes:

> EA> In theory we could have a Gnus that fires off all the servers and
> then EA> returns control to the user immediately
> https://github.com/dickmao/gnus does just that.  It's about a 3500
> line change.  Perhaps 1-2 years from now I will make a concerted
> effort to merge, but given,
>
> 1. the changes are not true multithreading, and 2. gnus users, being
> of a different generation, are generally content to manually retrieve
> and block,
>
> I give the integration less than 50% chance of seeing the light of day.

Interesting! Is this the same patchset you proposed on emacs.bugs a
while ago? I understood that that was about threading, but didn't
realize that the fetch process actually returned immediately. How do you
handle the "surprise" updating, from the user's point of view?

I will take a look at your repo when I have time for more Gnus
deep-dives, which should be in... less than 1-2 years from now? I hope.
I see that you're getting rid of global
gnus-summary-buffer/gnus-article-buffer, and I think those are great
changes regardless of whatever else comes on top of that. Would you be
interested in getting those changes in first?

Eric



  reply	other threads:[~2020-08-21 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21  4:06 Wayne Harris
2020-08-21  4:39 ` Eric Abrahamsen
2020-08-21 10:31   ` dick.r.chiang
2020-08-21 17:42     ` Eric Abrahamsen [this message]
2020-08-21 14:18   ` Wayne Harris
2020-08-21 17:16     ` Eric Abrahamsen
2020-08-21 20:30       ` Wayne Harris
2020-08-22  2:27         ` Wayne Harris
2020-08-22 10:45           ` dick.r.chiang
2020-08-22 15:52             ` Wayne Harris
2020-08-22 16:11               ` dick.r.chiang
2020-08-22 17:07                 ` Eric Abrahamsen

Reply instructions:

You may reply publicly 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rjzvqsu.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).