169
edits
CloudServices/Notifications/Specification: Difference between revisions
Jump to navigation
Jump to search
m
CloudServices/Notifications/Specification (view source)
Revision as of 21:37, 14 April 2011
, 14 April 2011→Set Up an Additional Client
m (→Client ToDo) |
|||
| Line 74: | Line 74: | ||
=== Set Up an Additional Client === | === Set Up an Additional Client === | ||
One of the main advantages of the service is it allows users to receive notifications on multiple clients, be it their browser, mobile phone, etc. Thus setting up another client to receive notifications is likely to be a common operation. The following are two possible methods the user can use to set up an additional client. | One of the main advantages of the service is it allows users to receive notifications on multiple clients, be it their browser, mobile phone, etc. Thus setting up another client to receive notifications is likely to be a common operation. The following are two possible methods the user can use to set up an additional client (note: the goal is to have this be virtually identical to Firefox Sync). | ||
<ul> | |||
<li>'''Option A: Using JPAKE'''<br /> | |||
JPAKE is a mechanism for securely exchanging keys between two clients. This is the same process that is used by the Sync service when adding a new device. | JPAKE is a mechanism for securely exchanging keys between two clients. This is the same process that is used by the Sync service when adding a new device. | ||
</li> | |||
<li>'''Option B: Using Credentials and Secret Key'''<br /> | |||
If the user does not have a client that is already connected, they will have to have their credentials ready along with their secret key (which is used to decrypt the messages sent to them). Provided they have this information, the following process could also be used to connect a new client: | If the user does not have a client that is already connected, they will have to have their credentials ready along with their secret key (which is used to decrypt the messages sent to them). Provided they have this information, the following process could also be used to connect a new client: | ||
| Line 87: | Line 88: | ||
# User enters credentials along with their secret key. | # User enters credentials along with their secret key. | ||
# Client registers itself with the notification server. | # Client registers itself with the notification server. | ||
</li> | |||
</ul> | |||
'''Related Use Cases''': [[#Register with Notifications Service|Register with Notifications Service]] | '''Related Use Cases''': [[#Register with Notifications Service|Register with Notifications Service]] | ||