Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Asynchronous backend interface
Date: 13 Nov 1997 22:19:37 +0100	[thread overview]
Message-ID: <m3u3dg5w5y.fsf@sparky.gnus.org> (raw)
In-Reply-To: Greg Stark's message of "07 Nov 1997 02:28:38 -0500"

Greg Stark <gsstark@MIT.EDU> writes:

> Wouldn't it be wonderful if you could check for new news while editting a
> buffer. Or Gnus was capable of querying more than one backend at the same
> time? Or if you could be reading one group while generating a particularly
> large summary buffer at the same time?

[...]

> If you don't believe me that this would be possible check the
> archives for the two previous times i've proposed this, the first
> would be near the September Gnus code freeze, and the second
> sometime during Red Gnus development.

Oops.  I think Quassia Gnus just went into feature freeze.  :-)

> It wouldn't be useful for everyone all the time. If you have a very fast
> network connection your emacs might be unresponsive handling i/o. But if you
> have a handful of slow foreign servers it would be very useful to scan them
> while also getting all the quick stuff at the same time. If you have a slow
> network connection it would just be nice to be able to download large summary
> buffers without locking up your emacs while they download.

Yes, it would be nice, but it will be quite a bit of work to get it to
work ok.  It's something I can't do anytime soon.

(The code freeze thing was a joke, though.)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1997-11-13 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-07  7:28 Greg Stark
1997-11-13 21:19 ` Lars Magne Ingebrigtsen [this message]

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=m3u3dg5w5y.fsf@sparky.gnus.org \
    --to=larsi@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).