SoC:RoamingSupport: Difference between revisions

← Older edit

SoC:RoamingSupport (view source)

Revision as of 00:44, 28 August 2007

41 bytes removed , 28 August 2007

→‎TODO List

Kreeger

26

edits

@@ Line 18: / Line 18: @@
 <div style="text-align: center">[[Image:update_messages.png]]</div>
-=== Delta Update Messages ===
+=== Update Messages ===
-The idea of storage on either the IMAP or POP3 level involves the use of a complete sync message, and corresponding delta messages for each update since the last complete sync message.
+For containing and controlling the data between installations, update messages are used to package and transport the sync data. All sync information is packed into a file. There are two types of update messages:
-We would like to store these messages somewhere other than the INBOX, and would like to avoid the end-user discovering these messages as much as possible. To hide these update messages in the IMAP implementation, we would probably take advantage of an un-subscribed folder. For the POP3 version, we would set some sinks in the POP3 protocol implementation to process our update message, and leave them out of the users inbox.
+* Full Update Message - Contains everything that the user has selected to sync
+* Delta Update Message - Contains only the changes since the last full/delta update message.
-To prevent any confusion, the subject of each delta message would be clearly labeled.
+Some of the sync data can be transferred as the full data file, like the address book's abook.mab file. However, certain data types like user preferences can not be sync'd this way, and contain an update log listed in the file. To help with unpacking all of the data, a TOC file is created and included with each update message. The format of the TOC file looks like this:
-To prevent potential malicious emails from doing bad things during the update, we plan to sign our messages using a PIN implementation. This setup will be similar to the Google Sync feature.
-For keeping things simple, each update message will incorporate a TOC file. The format of the TOC file will look like:
    NumItems: 3
@@ Line 33: / Line 30: @@
    Item1: temp.txt
    Item2: temp2.txt
-This plain text format will make it easy for the roaming service to obtain attachments w/o having to run through libmime.
 === Delivery Options ===
@@ Line 52: / Line 47: @@
 For IMAP-synched sessions, a timer is probably not needed, as changes can be applied as new delta/update messages are posted. The same philosophy can be applied to the POP3 setting, applying sync changes based on the biff-update interval.
+== TODO List ==
+To help keep things centralized, I'm keeping track of things I need to work on here. Any suggestions made by others will be listed here as well.
+* Shutdown &amp; Refresh AB Datasource
+* Mark Update Messages as Read (IMAP not working right?)
+* Fix Purge Update Messages
+* Initial/Temporary UI integration
+* Sign Update Messages [file follow-up bug]
+* Include information to setup a roaming account from a full update message.
+* POP3 mailboxes that have a limited download size will fully download the entire update message
+** [http://mxr.mozilla.org/mailnews/source/mailnews/base/util/nsMsgIncomingServer.cpp#1737 Use an internal filter].
+** [http://mxr.mozilla.org/mailnews/source/mailnews/base/util/nsMsgIncomingServer.cpp#1629 Or read the filter from a file].
 == Service Synchronization Notes ==
@@ Line 67: / Line 75: @@
 ** shutdown
-== Things to keep in mind: ==
-* Make the feature extensible
-** A simple interface to inherit?
-* Need a way to know that an object has changed
-* A way to stream the object to a file, or a file pointer
-** for newsrc files, filters, (anything that uses a file)
-* Things that aren't stored as a file:
-** Account Information
-** About everything in account.js
-*** Sync tag definitions
-** An interface that parses and applies these changes:
-----
 == Item Synchronization Notes and Ideas ==