From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Asynchronous nntp.el
Date: 19 Jan 1996 04:36:00 +0100 [thread overview]
Message-ID: <w8s3f9cdffj.fsf@eistla.ifi.uio.no> (raw)
I have rewritten nntp.el to be totally asynchronous. Process filters,
callback functions -- a very flexible architecture. I'm moving the
`nntp-asynchronous-' stuff (that was used for article prefetching) up
into the Gnus code proper, so that all other future backends capable
of being asynchronous don't have to duplicate that code. (For
instance -- there's no reason why nnml using ftp to read messages
shouldn't be asynchronous.)
When I get the whole thing working properly, writing functions for
postponed commands (and stuff) shouldn't be much work.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next reply other threads:[~1996-01-19 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-19 3:36 Lars Magne Ingebrigtsen [this message]
1996-01-19 5:33 ` William Perry
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=w8s3f9cdffj.fsf@eistla.ifi.uio.no \
--to=larsi@ifi.uio.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).