9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@9fans.net
Subject: Re: [9fans] store 9p session-only values using lib9p
Date: Thu, 12 Jun 2008 16:49:03 +0200	[thread overview]
Message-ID: <c9aea15fa3a2815e365b47d79daccb3f@lsub.org> (raw)
In-Reply-To: <3bd9fd157a7ee4567da63233405e130e@quanstro.net>

>  > But the nice thing is that you can edit text, copy attachments in/out,
>  > remove them, etc. etc.
>  this is already possible with upas/fs, isn't it? also, i get the benefit
>  of not being tied into message formats. for example, i can use imap.

Nope. If you try to remove an attach you remove the mail.
What I like of your way  is that making upas/fs understand this mbox format makes
all other tools available.

>  in addition, doesn't storing mail your way increase the storage requirements?

No. Same file sent multiple times with different mails (which I do get a lot) only
consumes a single place on venti.

>  also, what do you do about header parsing without upas/fs's help?

I run upas/fs on the raw file (e.g., in the Send script that sends this reply)

>  (storing small mailboxes as a mdir even consumes more resources than
>  a mbox. unfortunately, i have to account for massive mail boxes.)

(are there small mboxes anymore? ;)

I know, but it's so covenient to do a "looktags msgs quanstro mbox" and get the
paths/lines for messages relevant; etc.




  reply	other threads:[~2008-06-12 14:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 20:06 gdiaz
2008-06-11 20:48 ` Russ Cox
2008-06-11 20:58   ` gdiaz
2008-06-11 23:44 ` erik quanstrom
2008-06-12  0:01   ` [9fans] upas/fs Russ Cox
2008-06-12  2:31     ` erik quanstrom
2008-06-12  2:59       ` Lyndon Nerenberg
2008-06-12  8:34   ` [9fans] store 9p session-only values using lib9p gdiaz
2008-06-12 10:04     ` erik quanstrom
2008-06-12 10:24       ` Fco. J. Ballesteros
2008-06-12 10:28         ` Fco. J. Ballesteros
2008-06-12 10:39         ` gdiaz
2008-06-12 10:43           ` Francisco J Ballesteros
2008-06-12 10:55             ` gdiaz
2008-06-12 11:04               ` Francisco J Ballesteros
2008-06-12 11:11                 ` gdiaz
2008-06-12 17:16                 ` lucio
2008-06-12 12:25         ` erik quanstrom
2008-06-12 12:32           ` erik quanstrom
2008-06-12 14:03           ` Francisco J Ballesteros
2008-06-12 14:25             ` erik quanstrom
2008-06-12 14:49               ` Fco. J. Ballesteros [this message]
2008-06-12 14:55                 ` Fco. J. Ballesteros
2008-06-12 15:06                 ` erik quanstrom
2008-06-12 17:12         ` lucio
2008-06-12 10:26       ` gdiaz
2008-06-12 11:09         ` erik quanstrom
2008-06-12 13:29           ` gdiaz
2008-06-12 14:10           ` Russ Cox
2008-06-12 14:10             ` erik quanstrom

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=c9aea15fa3a2815e365b47d79daccb3f@lsub.org \
    --to=nemo@lsub.org \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).