Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: Sup developers <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup-server revisited
Date: Tue, 22 Feb 2011 22:17:04 +0200	[thread overview]
Message-ID: <1298400274-sup-4941@tilus.net> (raw)
In-Reply-To: <1298320404-sup-5972@masanjin.net>

William Morgan, 2011-02-21 23:02:
> I have been making a lot of
> progress in a short amount of time.

Cool!  I'm thrilled.  \o/

> - 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.

I guess this offers the possibility to add threading to "external
state" of messages, together with labels.  I'd do a whole a lot of
more prune'n'crafting with my threads if there only was more
comfortable interface to doing it (admit it, been too lazy to
implement it in sup).

Do you have considerations wrt to programmatical thread browsing and
editing API?  Something I've thought of, on the top of my head.

first_msg
|-- second_msg
|-- third_msg
|   `-- fifth_msg
`-- fourth_msg

sixth_msg
`-- seventh_msg

thread = Thread.find :second
subthread = thread.find { |msg| msg == :third_msg }.prune!
Message.find(:sixth_msg).craft! subthread

first
|-- second
`-- fourth

sixth
|-- third
|   `-- fifth
`-- seventh

> - Allow concurrent access from multiple clients.

Since the first post on sup-server I've been nurturing the idea of
"fat" sup-client for maemo/meego.

> - Borrow as much code as possible from the current Sup, because I
>   sure as shit don't want to have to rewrite it all.

Would it be time to go for https://github.com/mikel/mail now?  It
would be supported and actively developed and I really like the API.
As a downside, depending on activesupport pulls in a whole a lot of
fluff and using treetop may suggest that parsing might hog a little
more cpu and memory than is absolutely necessary.

Who would give us bindings to GMime and wrap it inside Mail API...

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  parent reply	other threads:[~2011-02-22 20:33 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
2011-02-22 20:17 ` Tero Tilus [this message]
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=1298400274-sup-4941@tilus.net \
    --to=tero@tilus.net \
    --cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox