Gnus development mailing list
 help / color / mirror / Atom feed
From: Wayne Harris <wharris1@protonmail.com>
To: ding@gnus.org
Subject: Re: is there a possibility for gnus to download data without blocking?
Date: Fri, 21 Aug 2020 17:30:08 -0300	[thread overview]
Message-ID: <86eenzeo8f.fsf@protonmail.com> (raw)
In-Reply-To: <875z9bvs13.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

[...]

>>> In theory we could have a Gnus that fires off all the servers and then
>>> returns control to the user immediately, but that would involve handling
>>> out-of-band returns as they came in from the servers, and Gnus would
>>> have to be structured very differently than it is now to manage that.
>>
>> I don't expect ever to be able to download a bunch of data and have it
>> all very fast on my screen.  But I do think that a system being always
>> faster than the user gives the user an impression of total control,
>> which is pleasurable.  So I would consider that a very nice improvement
>> for Gnus itself.
>
> The main issue is: if you get control of Emacs back right away, what
> happens when the server response comes in? Work still needs to be done
> to parse the response and incorporate it into Gnus' state, and that work
> needs to be done in lisp, which means the user is probably going to get
> interrupted again, to some extent.

I would guess the result would be a lot better because EMACS is fast and
the network, slow.  You continue to use EMACS as the data comes in.
When it's all local, Gnus takes control of EMACS but finishes quickly
because ELISP is fast.  So you'd notice it a lot less, if at all.

> Let's see how Dick is handling it! :)

Yes, let's do that.  I bet it won't be easy for me, but I'll give it a
try after dinner today, that is, within 6 hours.  Expect my report.



  reply	other threads:[~2020-08-21 20:31 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
2020-08-21 14:18   ` Wayne Harris
2020-08-21 17:16     ` Eric Abrahamsen
2020-08-21 20:30       ` Wayne Harris [this message]
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=86eenzeo8f.fsf@protonmail.com \
    --to=wharris1@protonmail.com \
    --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).