Confirmed users
358
edits
Identity/AttachedServices/StorageServerProtocol: Difference between revisions
Identity/AttachedServices/StorageServerProtocol (view source)
Revision as of 13:46, 18 June 2013
, 18 June 2013→Authentication
No edit summary |
|||
| Line 89: | Line 89: | ||
* a short-lived id/key pair that can be used to authenticate subsequent requests using the Hawk request-signing scheme | * a short-lived id/key pair that can be used to authenticate subsequent requests using the Hawk request-signing scheme | ||
* a mapping of collection names to access URLs | * a mapping of collection names to access URLs | ||
You can think of this as establishing a "login session" with the server. Access requests for a specific collection should then be directed | You can think of this as establishing a "login session" with the server. Access requests for a specific collection should then be directed | ||
| Line 118: | Line 119: | ||
The collection-specific access URLs may include a unique identifier for the user, in order to improve RESTful-icity of the API. Or | The collection-specific access URLs may include a unique identifier for the user, in order to improve RESTful-icity of the API. Or | ||
they might point the client to a specific data-center which houses their write master for each collection. It's opaque to the client. | they might point the client to a specific data-center which houses their write master for each collection. It's opaque to the client. | ||
== Data Access == | == Data Access == | ||