Confirmed users
1,018
edits
CloudServices/Roadmaps/EditionServer: Difference between revisions
CloudServices/Roadmaps/EditionServer (view source)
Revision as of 17:28, 25 March 2013
, 25 March 2013→Requirements
| Line 92: | Line 92: | ||
** Version must be higher than previously submitted value (TODO: Need to provide use case for how versions would be required) | ** Version must be higher than previously submitted value (TODO: Need to provide use case for how versions would be required) | ||
</strike> | </strike> | ||
* Clients are the source of truth for the associated channels. | * Clients are the source of truth for the associated channels. | ||
** Channel discrepancies between the client and the server result in the server sending a request to client to reset. | ** Channel discrepancies between the client and the server result in the server sending a request to client to reset. | ||
*** TODO: Details on what a reset entails needed | |||
* | * UAIDs may be a globally unique 128 bit number | ||
* | * APPIDs are unique per UAID namespace | ||
* | * ENDPOINTs are Globally Unique | ||
* Data must be stored and managed in a highly responsive manner (low read/write latency) | * Data must be stored and managed in a highly responsive manner (low read/write latency) | ||
* | * EDITION SERVER should support 1MM+ number of simultaneously connected clients | ||
* Connections should maintain as long as possible. A server should not break a connection because it's gone idle. | * Connections should maintain as long as possible. A server should not break a connection because it's gone idle. | ||
* A Server should attempt to retry a failed transmission to the client every 60 seconds. | * A Server should attempt to retry a failed transmission to the client every 60 seconds. | ||