Gnus development mailing list
 help / color / mirror / Atom feed
From: dick.r.chiang@gmail.com
To: Wayne Harris <wharris1@protonmail.com>
Cc: ding@gnus.org
Subject: Re: is there a possibility for gnus to download data without blocking?
Date: Sat, 22 Aug 2020 06:45:05 -0400	[thread overview]
Message-ID: <87sgcf558u.fsf@dick> (raw)
In-Reply-To: <86o8n3bejo.fsf@protonmail.com> (Wayne Harris's message of "Fri, 21 Aug 2020 23:27:39 -0300")

I am gratified someone studied my changes.

WH> CODA ... and it's not clear what it is or what it does.

CODA merely updates the message counts in *Group* after retrieval threads
complete.

WH> But I think the real thing you wanted to know was how he would handle, for
WH> the situation the intermixing of different servers returning data ...

As the 90s pop song goes, one has to "keep'em separated."  This means making
"total war" on the monolithicity of the summary, article, and nntp buffers
which Gnus has since inception assumed global singletons.

WH> Same strategy as dickmao's, but using processes, not threads.
WH> If so, it would be way better if [Gnus] just wouldn't block.  Maybe we
WH> don't need dickmao's threads after all.

As EA previously stated, shunting all retrieval logic to a separate process B
still poses the serious problem of integrating B's results in
the main process A.  Moreover, multiple processes begs the ornery question
of interprocess communication, consumes more system resources,
and admits the likelihood of orphaned processes.





  reply	other threads:[~2020-08-22 10:46 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
2020-08-22  2:27         ` Wayne Harris
2020-08-22 10:45           ` dick.r.chiang [this message]
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=87sgcf558u.fsf@dick \
    --to=dick.r.chiang@gmail.com \
    --cc=ding@gnus.org \
    --cc=wharris1@protonmail.com \
    /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).