Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>, sup-talk@rubyforge.org
Subject: Re: [sup-talk] [sup-devel] sup-server revisited
Date: Wed, 23 Feb 2011 01:59:39 -0800 (PST)	[thread overview]
Message-ID: <4d64da8b.8389cc0a.31cf.6b21@mx.google.com> (raw)
In-Reply-To: <1298397585-sup-1661@masanjin.net>

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


  reply	other threads:[~2011-02-23 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 21:02 William Morgan
2011-02-22 14:09 ` Nicolas Pouillard
2011-02-22 18:00   ` [sup-talk] " William Morgan
2011-02-23  9:59     ` Nicolas Pouillard [this message]
2011-02-23 18:23       ` 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=4d64da8b.8389cc0a.31cf.6b21@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --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