From: Steinar Bang <sb@metis.no>
Subject: Re: Greg's Perennial Plea For an Asynchronous Backend Interface
Date: 04 Jan 2001 11:40:08 +0100 [thread overview]
Message-ID: <why9wrvbw7.fsf@viffer.computas.no> (raw)
In-Reply-To: <878zot5f28.fsf@localhost.freelotto.com>
>>>>> Greg Stark <gsstark@mit.edu>:
> All you need is an interface between Gnus and the backends that
> allows Gnus to pass a callback with a closure to the backend when an
> asynchronous call is permitted. And of course you want to do this in
> a backwards compatible way, so if the backend doesn't implement the
> asynchronous call Gnus just calls the normal backend function.
[snip!]
> Doing it properly requires the new interface between backends and
> Gnus. And it require Gnus be aware of when it's using the
> asynchronous interface to avoid conflicts. But it would be much more
> powerful than my kludge.
Is this basically the same thing that nnimap needs for its performance
enhancements?
next prev parent reply other threads:[~2001-01-04 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 6:23 Greg Stark
2001-01-03 15:55 ` Kai Großjohann
2001-01-04 1:26 ` Lloyd Zusman
2001-01-04 10:40 ` Steinar Bang [this message]
2001-01-05 10:30 ` Simon Josefsson
2001-01-05 16:41 ` Steinar Bang
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=why9wrvbw7.fsf@viffer.computas.no \
--to=sb@metis.no \
/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).