Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: terence.namusonge@gmail.com (teroz)
Subject: [sup-talk] rethinking sup part ii
Date: Wed, 23 Jul 2008 11:27:46 +0200	[thread overview]
Message-ID: <1f7abd640807230227v75c28a62v6c299242a9bf3303@mail.gmail.com> (raw)
In-Reply-To: <1216803452-sup-8333@port-ext16.ensta.fr>

Well surely if we r eschewing typical mail storage formats like mbox and
IMAP then a database is the way to go
unless your suggesting we write some form of storage library as well.

On Wed, Jul 23, 2008 at 10:58 AM, Nicolas Pouillard <
nicolas.pouillard at gmail.com> wrote:

> Excerpts from Richard Heycock's message of Wed Jul 23 10:45:06 +0200 2008:
> > Excerpts from William Morgan's message of Mon Jul 21 07:33:24 +1000 2008:
> > > In which the new version of Sup is described!
> > >
> > > http://all-thing.net/2008/07/rethinking-sup-part-ii.html
> >
> > I really like the idea and I have to say that I'm *very* glad that you
> > are keeping the ncurses interface.
> >
> > My one concern is that you are thinking of using Sphinx and as a
> > consequence you are relient on a relational database. Is that really
> > what you want for a mail client? I find this disturbing on two levels:
> > having a full blown database system for email seems like overkill and
> > the idea of an index bring based on a relational model quite appaling.
> >
> > There are a number of other indexs such as Xapian or Hyper Estraier
> > both have ruby bindings and both are quite mature and widely used in
> > other projects.
>
> I'm also concerned by using relying on relational databases for a mail
> service.
>
> --
> Nicolas Pouillard aka Ertai
>
> _______________________________________________
> sup-talk mailing list
> sup-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
>


-- 
--Teroz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080723/0dfa1626/attachment.html>


  reply	other threads:[~2008-07-23  9:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 21:33 William Morgan
2008-07-20 23:28 ` Guillaume Quintard
2008-07-21  0:04   ` William Morgan
2008-07-21  5:43     ` Guillaume Quintard
2008-07-21 12:14 ` Peter Krenn
2008-07-21 15:22   ` William Morgan
2008-07-21 15:26     ` Stephen Patterson
2008-07-21 16:04       ` John Bent
2008-07-22  2:12       ` William Morgan
2008-07-23 17:40         ` Nicolas Pouillard
2008-07-23 22:26           ` William Morgan
2008-07-24  9:16             ` Nicolas Pouillard
2008-07-21 18:43 ` Lionel Ott
2008-07-23  8:45 ` Richard Heycock
2008-07-23  8:58   ` Nicolas Pouillard
2008-07-23  9:27     ` teroz [this message]
2008-07-23 21:41       ` Richard Heycock
2008-07-23 17:09   ` William Morgan
2008-07-25 12:11     ` Marcus Williams
2008-07-24  4:55 ` Guarded Identity
2008-07-24  9:21   ` Nicolas Pouillard
2008-07-25 16:00     ` William Morgan
2008-07-26  7:32       ` Guarded Identity
2008-07-25  7:18   ` 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=1f7abd640807230227v75c28a62v6c299242a9bf3303@mail.gmail.com \
    --to=terence.namusonge@gmail.com \
    /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