Confirmed users
358
edits
Identity/AttachedServices/StorageServerProtocol: Difference between revisions
Jump to navigation
Jump to search
Identity/AttachedServices/StorageServerProtocol (view source)
Revision as of 06:57, 14 May 2013
, 14 May 2013no edit summary
No edit summary |
|||
| Line 226: | Line 226: | ||
* The provided batches had holes, or were otherwise invalid | * The provided batches had holes, or were otherwise invalid | ||
* The server forgot a previous batch and you'll have to start again | * The server forgot a previous batch and you'll have to start again | ||
== Things To Think About == | |||
* How do people feel about the separate "login" step. It's providing value to the server since it lets us tunnel some state information, but maybe it's not very nice from the client side? | |||
* Currently there's no explicit way for the server to track the current version held by each client. We could add this in the initial handshake, or intuit it based on their activity. | |||
* Is json the best format for this transfer, or could we come up with a more efficient representation? | |||
* Should we add a way to retrieve specific keys, for real-time updating of just the important bits? | |||