[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sup-talk] [sup-devel] sup-server revisited
On Tue, 22 Feb 2011 18:00:06 +0000, William Morgan <wmorgan-sup@masanjin.net> wrote:
> [resend to list]
>
> Reformatted excerpts from Nicolas Pouillard's message of 2011-02-22:
> > 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.
>
> I am definitely interested in a set of composable CLI tools that talk to the
> server, for basic operations like search, show, add/remove labels, etc.
Ok, then I think it would make not much sense to make it different than
notmuch. Of course with good arguments changes can go the other direction as
well.
> > 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.
>
> The server implementation is pretty heavily tied to a particular index and
> store mechanism. It's not clear to me how (or whether) the CLI tools will
> allow you to swap out different implementations.
I agree with you and don't to expose such details. What I want is a way to
separate the frontend from the backend completely. This would allow me to
use the frontend with any of:
- heliotrope
- sup (maybe)
- notmuch (not written in ruby)
- my own toy project (not in ruby either)
- any combination of both, where "writes" are dispatched to all of them,
and "reads" are dispatched to one of them (that I can change easily).
I also want to be able to script batch operations on the mail store easily.
Best regards,
--
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk