<-- initial sync request --> <-- no token = initial sync --> <-- if {root-folder-id} present, we start sync there rather than at folder 11 --> <-- if {earliest-message-date} present, omit all messages and respective conversation before the specified date in second(specified in s) This parameter honored in initial and delta sync as well--> <-- if {earliest-calendar-date} present, omit all appointments and tasks that don't have a recurrence ending after that time (specified in ms) This parameter honored in initial sync only --> <-- if {max-number-of-deleted-items} present and it is greater than 0, then response will limit to the number of deleted items to the value and if there are more delete queued, and another SyncRequest (using the returned token) is necessary. This attribute honored in delta sync only --> <-- if {max-number-of-modified-items} present and it is greater than 0, then response will limit to the number of modified items to the value and if there are more modified items queued, and another SyncRequest (using the returned token) is necessary. maximum value for changeLimit = 3990 if client send greater value in soap call, It will restricted to 3990 by server. This attribute honored in delta sync only --> <-- subsequent delta sync request --> <-- handle deletes first --> <-- modified/created folders (none here) --> <-- modified/created tags (none here) --> <-- other modified/created things (only id/folder/date means new or content changed) */ <-- sync on other mailbox is done via specifying target account in SOAP header --> <-- if we're delta syncing on another user's mailbox and any folders have changed: --> <-- if there are now no visible folders, you'll get an empty element --> <-- if there are any visible folders, you'll get the full visible folder hierarchy --> <-- if a {root-folder-id} other than the mailbox root (folder 1) is requested --> <-- or if not all folders are visible when syncing to another user's mailbox, --> <-- all changed items in other folders are presented as deletes --> <-- client resolves conflicts and passes back its changes --> <-- client goes through the front door (e.g. ConvAction, etc.) --> Khavari Brunhilde bk@hotmail.com <-- client does another sync and gets back: --> <-- * any changes they just made --> <-- * any externally-caused changes since the last sync --> <-- if typed="1" is specified on the SyncRequest, deletes are also broken down by item type --> <-- if the response is a mail.MUST_RESYNC fault, client has fallen too far out of date and must re-initial sync --> <-- handle deletes first --> <-- modified/created folders --> <-- modified/created tags (none here) --> <-- other modified/created things (only id/folder/date means new or content changed) */ <-- if more="1" is specified on the sync response, the response does *not* bring the client completely up to date. more changes are still queued, and another SyncRequest (using the new returned token) is necessary. --> <-- handle deletes first --> <-- handle deletes first -->