192
edits
| Line 206: | Line 206: | ||
<code>Identity</code> contains all the personal outgoing mail information | <code>Identity</code> contains all the personal outgoing mail information | ||
for a given person. Although all account types can have multiple associated identities by design, | for a given person. Although all account types can have multiple associated identities by design, RSS do not need this entity, as does any other account that does not interact with compose code. | ||
<code>AddressBook</code> is the central repository of the user's contacts. | <code>AddressBook</code> is the central repository of the user's contacts. | ||
MORE INFO NEEDED HERE ABOUT ITS RELATION TO OTHER ENTITIES | MORE INFO NEEDED HERE ABOUT ITS RELATION TO OTHER ENTITIES | ||
<code>Folder</code> is the logical entity of message contents. Every account has a root folder, which has several subfolders (each potentially with their own subfolders, ad infinitum) which are actual folders on the hosting operating system. | <code>Folder</code> is the logical entity of message contents. Every account has a root folder, which has several subfolders (each potentially with their own subfolders, ad infinitum) which are actual folders on the hosting operating system for local folders and summary files for IMAP and NNTP folders. | ||
<code>Database</code> component, on the other hand, is the physical store of message headers in '''Mork''' format. This store is the '''msf''' file, e.g. Inbox.msf or mozilla.dev.apps.thunderbird.msf. | <code>Database</code> component, on the other hand, is the physical store of message headers in '''Mork''' format. This store is the '''msf''' file, e.g. Inbox.msf or mozilla.dev.apps.thunderbird.msf. | ||
edits