36
edits
SoC:RoamingSupport: Difference between revisions
m
no edit summary
mNo edit summary |
|||
| Line 5: | Line 5: | ||
The pull operation would request data (again in a to-be-determined structure) from the object into the synchronization service. | The pull operation would request data (again in a to-be-determined structure) from the object into the synchronization service. | ||
=== Delta 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. | |||
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. | |||
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. | |||
== Delivery == | == Delivery == | ||