39 |
Rationale |
Rationale |
40 |
--------- |
--------- |
41 |
|
|
42 |
We nedd a system for saving emails in Storm. (especially |
We need a system for saving emails in Storm (especially |
43 |
for the planned email-client.) A way to do this is to put |
for the planned email-client.) so we can transclude and |
44 |
all existent headers in one block and to put all bodies |
link. A way to do this is to put all headers of the mail |
45 |
in distinctive blocks, as said in ``Issues`` und described |
(In the case of a multipart-message there could be |
46 |
further later on. |
sub-headers for each part) in one block and to put all |
47 |
|
bodies in different blocks, as said in ``Issues`` and |
48 |
|
described further later on. |
49 |
|
|
50 |
The reason for putting the the bodies in separate blocks is |
The reason for putting the the bodies in separate blocks is |
51 |
that their content has xanalogical IDs, so we are able to |
that their contents so have xanalogical IDs, which don't |
52 |
transclude and link them. Another point is that different |
depend on the mail-header. So if one recives mails with |
53 |
e-mail header could point at the same body block. |
the same body but different headers the body will only be |
54 |
|
stored once and the headers point to the body's content |
55 |
|
using only one xanalogical ID. |
56 |
|
|
57 |
And it should be possible to fetch emails on different |
And it should be possible to fetch emails on different |
58 |
computers and to synchronize the Storm-Pool. |
computers and to synchronize the Storm-Pool. |