From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: RFC: message property API
Date: Sun, 22 May 2016 11:28:57 -0300 [thread overview]
Message-ID: <1463927339-5441-1-git-send-email-david@tethera.net> (raw)
People (or maybe just dkg) have proposed various bits of user metadata
to attach to messages
- references to be added or blacklisted
- encryption related key material
Since such metadata would be not-reproducible from the message files,
it would be "precious" and need a backup/restore path.
This is a prototype of a library API to support that.
Some things to note:
- This is tested on top of my libconfig [1] series, but I think there is no
logical dependency
- there are no docs, see the tests
- this is just the low level api; it would need to be extended in a
similar way to the libconfig series to dump and restore metadata.
This might require modifying/extending the API to dump all properties
for a message. That should be a relatively small change.
- it also be useful to be able delete all (key,value) pairs with a given
key.
- this should really go through the existing caching mechanism used by
e.g. tags, or at least not invalidate that cache.
[1] id:1463135893-7471-6-git-send-email-david@tethera.net
next reply other threads:[~2016-05-22 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 14:28 David Bremner [this message]
2016-05-22 14:28 ` [RFC patch 1/2] lib: refactor _notmuch_message_has_term David Bremner
2016-05-22 14:28 ` [RFC patch 2/2] RFC message-property API David Bremner
2016-05-30 11:49 ` message properties, round 2 David Bremner
2016-05-30 11:49 ` [RFC2 Patch 1/5] lib: read "property" terms from messages David Bremner
2016-05-30 11:49 ` [RFC2 Patch 2/5] lib: private string map (associative array) API David Bremner
2016-05-30 11:49 ` [RFC2 Patch 3/5] lib: basic message-property API David Bremner
2016-05-30 11:49 ` [RFC2 Patch 4/5] lib: extend private string map API with iterators David Bremner
2016-05-30 11:49 ` [RFC2 Patch 5/5] lib: iterator API for message properties David Bremner
2016-06-01 1:12 ` David Bremner
2016-06-01 1:52 ` Daniel Kahn Gillmor
2016-06-01 5:04 ` Tomi Ollila
2016-06-01 10:04 ` David Bremner
2016-06-01 14:13 ` Daniel Kahn Gillmor
2016-06-01 23:29 ` David Bremner
2016-06-02 17:33 ` Daniel Kahn Gillmor
2016-06-03 12:54 ` David Bremner
2016-06-03 14:38 ` Daniel Kahn Gillmor
2016-06-03 23:12 ` David Bremner
2016-06-04 16:23 ` Daniel Kahn Gillmor
2016-06-05 10:24 ` [PATCH] doc: document notmuch-dump header line David Bremner
2016-06-05 22:23 ` David Bremner
2016-06-06 6:38 ` Tomi Ollila
2016-06-07 10:55 ` David Bremner
2016-06-01 4:38 ` [RFC2 Patch 5/5] lib: iterator API for message properties Tomi Ollila
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463927339-5441-1-git-send-email-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).