Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] Persistence between IMAP clients
Date: Thu, 07 Feb 2008 08:45:33 +0000	[thread overview]
Message-ID: <1202373660-sup-5293@tomsk> (raw)
In-Reply-To: <1202248916-sup-1460@south>

On 5.2.2008, William Morgan wrote:
> Reformatted excerpts from William Morgan's message of 2008-02-05:
> > Sup will probably never work well in this kind of setup.
> 
> Until we make SupServer!

I never know if you're joking when you say stuff like this :) Joking
aside though, if you treat sup as a frontend for a database (which is
basically what it is forgetting the email client side) all you
actually need is to get ferret to run as a server.... and if thats all
you need perhaps we can use the work on the DRb server for the RoR
act_as_ferret plugin and have a remote index that sup can then be a
client of.

This then leads me to a wishlist item - perhaps the contacts stuff
should be moved into a ferret db. That way sup can be a searchable
contacts db as well (and it can be remote so shared across clients).

Any thoughts?

Marcus


  parent reply	other threads:[~2008-02-07  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 15:12 Gabriel Sean Farrell
2008-02-04 18:46 ` John Bent
2008-02-05 21:03   ` Gabriel Sean Farrell
2008-02-05 16:42 ` William Morgan
2008-02-05 19:12   ` Magnus Therning
2008-02-05 19:51     ` William Morgan
2008-02-05 21:11   ` Gabriel Sean Farrell
2008-02-05 22:02   ` William Morgan
2008-02-06 22:37     ` Gabriel Sean Farrell
2008-02-07  8:45     ` Marcus Williams [this message]
2008-02-07 18:12       ` William Morgan
2008-02-07 20:12         ` Gabriel Sean Farrell
2008-02-07 21:09         ` Marcus Williams

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=1202373660-sup-5293@tomsk \
    --to=marcus-sup@bar-coded.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