[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz-commits] gzz/doc/pegboard/email_storage--marc peg.rst
From: |
Marc Schiereck |
Subject: |
Re: [Gzz-commits] gzz/doc/pegboard/email_storage--marc peg.rst |
Date: |
Thu, 31 Oct 2002 00:56:41 +0100 |
User-agent: |
Mutt/1.3.28i |
Hi,
On Thu, Oct 31, 2002 at 12:06:38AM +0100, Benja Fallenstein wrote:
> >+We nedd a system for saving emails in Storm. (especially
> >+for the planned email-client.)
> >
>
> What else? I think a reader would want to know this ;-)
What exactly do you mean? More reasons to store emails in Storm-Pools?
> >A way to do this is to put
> >+all existent headers in one block and to put all bodies
> >+in distinctive blocks, as said in ``Issues`` und described
> >+further later on.
> >
>
> That's saying that *all* headers (of *all* emails) are put into the same
> block-- nonsense :)
true *g*
> s/distinctive/distinct/, or maybe better even "different"
It's always so hard to make a decision :8)
> >+The reason for putting the the bodies in separate blocks is
> >+that their content has xanalogical IDs,
> >
>
> It would have xanalogical IDs if we put it in the same block, too. The
> point is simply that if we receive the same message with the same body
> twice, but with different headers, the body should only be stored once,
> and links to and transclusions of it should only use a single
> xanalogical ID, so that links to one copy of the body will also be to
> the other copy of the body.
ok. I shouldn't have shorten it so much.
> >+And it should be possible to fetch emails on different
> >+computers and to synchronize the Storm-Pool.
> >
>
> Can you explain *why* this is made possible, or is that too hard?
At the moment I'm unsure, I'll ask you tomorrow (today :8) if I have
a question. Is what you wrote in the other mail an (at least partly)
explanation why this is made possible?