Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Attaching notes to messages
Date: 10 Oct 1999 22:38:59 +0200	[thread overview]
Message-ID: <vafln9b54t8.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jonas Steverud's message of "10 Oct 1999 21:59:34 +0200"

Jonas Steverud <d4jonas@dtek.chalmers.se> writes:

> One idea: For backends that allow writing, e.g. nnfolder, nnmh and
> nnml, we can add an "X-Gnus-Annotaion: 5673762". The problem is for
> backends like nntp that doesn't allow writing.

Well, we have the cache, and it ought to be possible to edit the
cached copy of a message, right?

OT1H, it seems to be a good idea to keep the annotation information in
the .newsrc.eld file, but I'm thinking of nnimap users where all state
information is supposed to be kept on the server.  Hm.  With article
editing, we could create a special nnimap group for annotations and
put them there.  The X-Gnus-Annotation header would then contain the
identifier of the corresponding article in the annotation group.

Sadly, both choices seem to be less than ideal :-(

kai
-- 
Life is hard and then you die.


  parent reply	other threads:[~1999-10-10 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-10 14:58 Hannu Koivisto
1999-10-09 16:36 ` François Pinard
     [not found]   ` <wtn1zb3rnq1.fsf@licia.dtek.chalmers.se>
1999-10-09 20:56     ` François Pinard
1999-10-11 10:58       ` Eric Marsden
1999-10-12  8:18         ` storing messages in DBMSes (Was: Attaching notes to messages) Steinar Bang
1999-10-12 11:16           ` Eric Marsden
1999-10-12 11:54             ` Fabrice POPINEAU
1999-10-10 20:38     ` Kai Großjohann [this message]
1999-10-10 18:53 ` Attaching notes to messages Harry Putnam
1999-10-10 23:29   ` Hannu Koivisto
1999-10-11  0:15     ` Harry Putnam

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=vafln9b54t8.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).