Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] GSoC Project of Interest
Date: Thu, 23 Apr 2009 05:52:56 -0700	[thread overview]
Message-ID: <1240490917-sup-3402@entry> (raw)
In-Reply-To: <1240449619-sup-9301@junction.es.net>

Reformatted excerpts from Jon Dugan's message of 2009-04-22:
> Most services on Plan 9 are implemented as synthetic file systems.
> The synthetic filesystem that represents email on Plan 9 is known as
> upas.  upas provides a filesytem view of mail boxes regardless of
> their backend storage medium (eg, POP, IMAP, etc) which provides a
> nice clean separation between the code that you use to do useful
> things to your mail and the code that deals with the mail store
> itself.

Very interesting and that's a great abstraction. Definitely lots of
overlap with STS. I suspect the primary differences will be that STS
uses fielded, full-text search as its primary access mechanism, and
there's no notion of any kind of filesystem-like mailbox or directory
hierarchy.
-- 
William <wmorgan-sup at masanjin.net>


      reply	other threads:[~2009-04-23 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  1:35 Jon Dugan
2009-04-23 12:52 ` William Morgan [this message]

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=1240490917-sup-3402@entry \
    --to=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