Privacy/Reviews/Firefox Home: Difference between revisions

Line 187: Line 187:
User data will sharded over a number of database servers. We will use a simple hashing mechanism so that we can determine where a user's data lives based on for example their username.
User data will sharded over a number of database servers. We will use a simple hashing mechanism so that we can determine where a user's data lives based on for example their username.


Each database will contain a plaintext version of the user's sync data. Initially that means bookmarks, history and tabs. The data will be normalized a bit more than it currently is in the Sync Servers so that it is easier to query for things.
Each database will contain a plaintext version of the user's sync data. Initially that means bookmarks, history and tabs. The data will be normalized and properly indexed a bit more than it currently is in the Sync Servers so that it is easier to query for things.


All data for all users will be stored in a single database. This means that all records have a unique username or userid field to connect them to a specific user. Queries will have to be properly constructed to follow this.
All data for all users will be stored in a single database. This means that all records have a unique username or userid field to connect them to a specific user. Queries will have to be properly constructed to follow this.
Line 210: Line 210:
'''Communication with Crypto Proxy'''  
'''Communication with Crypto Proxy'''  


{| class="wikitable"
None
|-
! Direction
! Message
! Data
! Notes
|-
| ''In:''
| message 1
| types of data received from component Y with the message
|
|-
| ''Out:''
| message 2
| types of data sent to component Y with the message
|
|}


'''Communication with [[Services/Sync|Sync Server]]'''  
'''Communication with [[Services/Sync|Sync Server]]'''  


{| class="wikitable"
None
|-
 
! Direction
'''Communication with [[Services/Sync|Sync Server]]'''
! Message
! Data
! Notes
|-
| ''In:''  
| message 1
| types of data received from component Y with the message
|
|-
| ''Out:''
| message 2
| types of data sent to component Y with the message
|
|}


=== Memcache Servers ===
=== Memcache Servers ===
Confirmed users
971

edits