383
edits
Line 31: | Line 31: | ||
== Exported APIs == | == Exported APIs == | ||
* Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.) | * Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.) | ||
** Various javascript modules into resource://gre/modules/accountmanager | |||
** '''service.jsm''' API for getting realms from the UI | ** '''service.jsm''' API for getting realms from the UI | ||
** '''profiles.jsm''' provide a way to register new account types | ** '''profiles.jsm''' provide a way to register new account types | ||
*** Also provides abstract parent classes for profiles to implement | *** Also provides abstract parent classes for profiles to implement | ||
*** savedAccountCount, savedAccounts, createAccount, connect, disconnect | *** savedAccountCount, savedAccounts, createAccount, connect, disconnect | ||
** base.jsm parent class sharing helper functions | ** base.jsm parent class sharing helper functions | ||
** cache.jsm simple fifo cache | ** cache.jsm simple fifo cache | ||
Line 45: | Line 45: | ||
* Does it interoperate with a web service? How will it do so? | * Does it interoperate with a web service? How will it do so? | ||
** Interacts with websites that provide AMCD and status headers | |||
* Explain the significant file formats, names, syntax, and semantics. | * Explain the significant file formats, names, syntax, and semantics. | ||
** AMCD describes to the browser how to connect/disconnect/get status and how to respond on success/failure, e.g., load a url | |||
** AMCD is a JSON file | |||
* Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully? | * Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully? | ||
* Does it change any existing interfaces? | * Does it change any existing interfaces? |
edits