[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] gzz/doc/pegboard/email_storage--marc peg.rst
From: |
Marc Schiereck |
Subject: |
[Gzz-commits] gzz/doc/pegboard/email_storage--marc peg.rst |
Date: |
Thu, 31 Oct 2002 16:30:45 -0500 |
CVSROOT: /cvsroot/gzz
Module name: gzz
Changes by: Marc Schiereck <address@hidden> 02/10/31 16:30:44
Modified files:
doc/pegboard/email_storage--marc: peg.rst
Log message:
update
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/email_storage--marc/peg.rst.diff?tr1=1.4&tr2=1.5&r1=text&r2=text
Patches:
Index: gzz/doc/pegboard/email_storage--marc/peg.rst
diff -u gzz/doc/pegboard/email_storage--marc/peg.rst:1.4
gzz/doc/pegboard/email_storage--marc/peg.rst:1.5
--- gzz/doc/pegboard/email_storage--marc/peg.rst:1.4 Wed Oct 30 17:54:17 2002
+++ gzz/doc/pegboard/email_storage--marc/peg.rst Thu Oct 31 16:30:44 2002
@@ -2,8 +2,8 @@
PEG email_storage
===============================================================
:Authors: Marc Schiereck
-:Date: $Date: 2002/10/30 22:54:17 $
-:Revision: $Revision: 1.4 $
+:Date: $Date: 2002/10/31 21:30:44 $
+:Revision: $Revision: 1.5 $
:Date-Created: 2002-10-28
:Status: incomplete
@@ -39,16 +39,20 @@
Rationale
---------
-We nedd a system for saving emails in Storm. (especially
-for the planned email-client.) 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.
+We need a system for saving emails in Storm (especially
+for the planned email-client.) so we can transclude and
+link. A way to do this is to put all headers of the mail
+(In the case of a multipart-message there could be
+sub-headers for each part) in one block and to put all
+bodies in different blocks, as said in ``Issues`` and
+described further later on.
The reason for putting the the bodies in separate blocks is
-that their content has xanalogical IDs, so we are able to
-transclude and link them. Another point is that different
-e-mail header could point at the same body block.
+that their contents so have xanalogical IDs, which don't
+depend on the mail-header. So if one recives mails with
+the same body but different headers the body will only be
+stored once and the headers point to the body's content
+using only one xanalogical ID.
And it should be possible to fetch emails on different
computers and to synchronize the Storm-Pool.