From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>,
sup-talk@rubyforge.org, sup-devel@rubyforge.org
Subject: Re: [sup-devel] sup-server revisited
Date: Tue, 22 Feb 2011 06:09:43 -0800 (PST) [thread overview]
Message-ID: <4d63c3a7.8389cc0a.52c5.7a5c@mx.google.com> (raw)
In-Reply-To: <1298320404-sup-5972@masanjin.net>
On Mon, 21 Feb 2011 21:02:28 +0000, William Morgan <wmorgan-sup@masanjin.net> wrote:
> Hello Sup fans,
[...]
> I'm focusing on the server component first. My specific goals are:
>
> - Encapsulate all storage and indexing logic.
> - Formalize the notion of labels and state, and the relationship between them,
> messages, and threads. Currently these relationships are fuzzy in Sup, and
> things suffer for it.
> - Precompute threads, so that search requires only moderate effort, instead of
> the large effort it does now. This will make search much, much faster, at the
> expense of a little more effort at index time.
> - Allow concurrent access from multiple clients.
> - Provide something that is transparent and easy to modify without having to go
> through an ncurses client.
On the server side, and more precisely on the interaction between the two,
I would love to see a simple Unix/command/CLI defined for the server. To make
myself clear, a bit like the notmuch CLI. This would allow for a greater
modularity and reusablity between components. For instance I would like to
index my mails with differents backends (disk is cheap), to get a way to
compare different tools on real data, when searching emails, and thus allow
to debug the different tools.
--
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-02-22 14:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:02 William Morgan
2011-02-22 13:46 ` Mark Alexander
2011-02-22 17:55 ` William Morgan
2011-02-22 18:44 ` Tero Tilus
2011-02-22 19:00 ` William Morgan
2011-02-22 14:09 ` Nicolas Pouillard [this message]
2011-02-22 20:17 ` Tero Tilus
2011-02-22 21:29 ` William Morgan
2011-02-23 9:48 ` Nicolas Pouillard
2011-02-23 18:43 ` William Morgan
2011-02-23 18:53 ` Alvaro Herrera
2011-02-23 21:08 ` William Morgan
2011-02-23 21:30 ` Alvaro Herrera
2011-03-03 19:38 ` Sascha Silbe
2011-02-26 19:15 ` Hamish
2011-02-26 22:04 ` William Morgan
2011-02-26 23:15 ` William Morgan
2011-03-01 19:38 ` Hamish
2011-03-02 12:43 ` Gregor Hoffleit
2011-03-02 18:51 ` William Morgan
2011-03-03 17:32 ` Gregor Hoffleit
2011-03-03 19:17 ` William Morgan
2011-04-15 10:46 ` Gregor Hoffleit
2011-04-15 17:16 ` William Morgan
2011-04-15 20:53 ` Gregor Hoffleit
2011-04-17 16:58 ` William Morgan
2011-04-17 17:55 ` William Morgan
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=4d63c3a7.8389cc0a.52c5.7a5c@mx.google.com \
--to=nicolas.pouillard@gmail.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.net \
/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