From: Steinar Bang <sb@metis.no>
Subject: Re: MIME message parts from backends (specifically IMAP)
Date: 05 Jan 1998 08:41:36 +0100 [thread overview]
Message-ID: <whvhvzs6z3.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Jan 1998 10:55:40 +0100"
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Steinar Bang <sb@metis.no> writes:
>> Would it be possible to change the backend interface, to allow access
>> to different parts of multipart messages?
> Since this would be primarily for IMAP, I think it would make more
> sense to do something specifically IMAP'y. Say, have a way to specify
> that the (mythical) IMAP backend only retrieve text parts of all
> messages by default, and then providing some way of accessing the
> remaining parts through buttons or pseudo-articles.
What I was thinking (and what probably would *really* get Rich's
hackles up :-) ), was that the (mythical) MIME parsing, and support
could be moved out into the backend, and that a uniform way to access
the message parts could be used across backends.
It's just a thought, motivated by a desire to do things in a uniform
way, even if it's less efficient, and complicates some parts.
How could you actually *do* something specifically IMAP'y? Gnus
doesn't know about anything except the standard backend operations,
does it?
- Steinar
next prev parent reply other threads:[~1998-01-05 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-01 15:17 Steinar Bang
1998-01-04 9:55 ` Lars Magne Ingebrigtsen
1998-01-05 7:41 ` Steinar Bang [this message]
1998-01-06 6:35 ` Lars Magne Ingebrigtsen
1998-01-06 16:50 ` Steinar Bang
1998-01-09 16:39 ` 守岡 知彦 / MORIOKA Tomohiko
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=whvhvzs6z3.fsf@norne.oslo.metis.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).