canmove, Confirmed users
725
edits
Service/Sync/FxSync/Developer/BrowserObjects: Difference between revisions
Jump to navigation
Jump to search
Service/Sync/FxSync/Developer/BrowserObjects (view source)
Revision as of 00:27, 30 November 2010
, 30 November 2010→bookmarks
| Line 9: | Line 9: | ||
In addition to these custom collection object structures, the [[Labs/Weave/Developer/StorageFormat#Payload:_Encrypted_Data_Object|Encrypted Data Object]] adds fields like <tt>id</tt> and <tt>deleted</tt>. Also, remember that there is data at the [[Labs/Weave/Developer/StorageFormat#Weave_Basic_Object|Weave Basic Object]] level as well such as <tt>id</tt>, <tt>modified</tt>, <tt>sortindex</tt> and <tt>payload</tt>. | In addition to these custom collection object structures, the [[Labs/Weave/Developer/StorageFormat#Payload:_Encrypted_Data_Object|Encrypted Data Object]] adds fields like <tt>id</tt> and <tt>deleted</tt>. Also, remember that there is data at the [[Labs/Weave/Developer/StorageFormat#Weave_Basic_Object|Weave Basic Object]] level as well such as <tt>id</tt>, <tt>modified</tt>, <tt>sortindex</tt> and <tt>payload</tt>. | ||
== bookmarks == | == bookmarks (engine version 1) == | ||
One bookmark record exists for each "bookmark item," where an item may actually be a folder or a separator. Each item will have a <tt>type</tt> that determines what other fields are available in the object. The following sections describe the object format for a given <tt>type</tt>. | One bookmark record exists for each "bookmark item," where an item may actually be a folder or a separator. Each item will have a <tt>type</tt> that determines what other fields are available in the object. The following sections describe the object format for a given <tt>type</tt>. | ||
| Line 15: | Line 15: | ||
Each bookmark item has a parentid and predecessorid to form a structure like a tree of linked-lists to provide a hierarchical ordered list of bookmarks, folders, etc. | Each bookmark item has a parentid and predecessorid to form a structure like a tree of linked-lists to provide a hierarchical ordered list of bookmarks, folders, etc. | ||
==== bookmark | ==== bookmark ==== | ||
This describes a regular bookmark that users can click to view a page. | This describes a regular bookmark that users can click to view a page. | ||
| Line 30: | Line 30: | ||
<b>predecessorid</b> <i>string</i>: GUID of the item before this (empty if it's first) | <b>predecessorid</b> <i>string</i>: GUID of the item before this (empty if it's first) | ||
<b>type</b> <i>string</i>: "bookmark" | <b>type</b> <i>string</i>: "bookmark" | ||
==== microsummary ==== | ==== microsummary ==== | ||
| Line 107: | Line 103: | ||
<b>predecessorid</b> <i>string</i>: GUID of the item before this (empty if it's first) | <b>predecessorid</b> <i>string</i>: GUID of the item before this (empty if it's first) | ||
<b>type</b> <i>string</i>: "separator" | <b>type</b> <i>string</i>: "separator" | ||
== bookmarks (engine version 2) == | |||
Same as engine version 1, except: | |||
* the predecessorid is removed from all records, | |||
* instead folder and livemark records have a children attribute which is an array of child GUIDs in order of their appearance in the folder | |||
== clients == | == clients == | ||