505
edits
Labs/Weave/Developer/HowToWriteClient: Difference between revisions
Labs/Weave/Developer/HowToWriteClient (view source)
Revision as of 21:45, 5 February 2010
, 5 February 2010→How to Write a Mozilla Services Client
(Created page with '= How to Write a Mozilla Services Client = The Mozilla Services platform provides always-on, server-side services to give our users a consistent web bro…') |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
= How to Write a | = How to Write a Weave Services Client = | ||
The [[Labs/Weave/Developer| | The [[Labs/Weave/Developer|Weave Services]] platform provides always-on, server-side services to give our users a consistent web browsing experience across all of their devices and programs. | ||
This page describes how you can use these services to construct a client that uses this data. With these services, you can read from, and write to, the user's browsing history, bookmarks, saved passwords, open tabs, form history, and preferences. | This page describes how you can use these services to construct a client that uses this data. With these services, you can read from, and write to, the user's browsing history, bookmarks, saved passwords, open tabs, form history, and preferences. | ||
| Line 13: | Line 13: | ||
The Weave service is defined using standard HTTP messages, JSON encodings, and well-defined cryptographic protocols, but your job will be much easier if you use one of the libraries. | The Weave service is defined using standard HTTP messages, JSON encodings, and well-defined cryptographic protocols, but your job will be much easier if you use one of the libraries. | ||
Check the [[Labs/Weave/Developer | Check the [[Labs/Weave/Developer#Libraries|Libraries]] section to see if your preferred language is supported yet; if not, you'll need to read the [[Labs/Weave/API|API]] pages and construct the appropriate network and cryptography calls yourself. | ||
2. In your application, securely prompt the user for their username, password, and passphrase. If this information is to be persisted to disk, consider using encryption on it to prevent a casual attacker from gaining access to secret credentials. | 2. In your application, securely prompt the user for their username, password, and passphrase. If this information is to be persisted to disk, consider using encryption on it to prevent a casual attacker from gaining access to secret credentials. | ||