[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: |
Benja Fallenstein |
Subject: |
Re: [Gzz-commits] gzz/doc/pegboard/email_storage--marc peg.rst |
Date: |
Thu, 31 Oct 2002 00:06:38 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1 |
Hi!
Marc Schiereck wrote:
Rationale
---------
- ...
+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 ;-)
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 :)
s/distinctive/distinct/, or maybe better even "different"
s/und/and/
+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.
+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?
Thx,
- Benja