canmove, Confirmed users
1,173
edits
CloudServices/Roadmaps/EditionServer: Difference between revisions
CloudServices/Roadmaps/EditionServer (view source)
Revision as of 19:54, 19 November 2013
, 19 November 2013Telliott moved page Services/Roadmaps/EditionServer to CloudServices/Roadmaps/EditionServer
m (Telliott moved page Services/Roadmaps/EditionServer to CloudServices/Roadmaps/EditionServer) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
<h1><i>PlaceHolder Server</i></h1> | <h1><i>PlaceHolder Server</i></h1> | ||
==Overview== | ==Overview== | ||
The Placeholder Server provides a SERVICE to allow third-party Application Servers to notify their Web Apps that an event has occurred and action may be required. The nature of this action will be defined by the app receiving the notification. | |||
The Placeholder Server is MINIMALIST. Setting up your own server should be a simple operation*. Because it runs over HTTP/Websockets, endpoints can be controlled by the user. (*offer of simplicity may not apply for connecting to proprietary networks, e.g. cell phones) | |||
The Placeholder Server is HIGH-CAPACITY. Each machine can handle hundreds of thousands of connected accounts and thousands of messages a second. | |||
The Placeholder Server is SCALABLE. Capacity can be increased in near-linear fashion by the addition of more machines. | |||
The Placeholder Server is AGNOSTIC. It does not validate the user or the channel. Any ping sent into the system will be accepted and made available to a client listening on that channel. | |||
The Placeholder Server is BEST EFFORT. It will do what it can to deliver the ping, and will succeed the vast majority of the time. If the ping is currently undeliverable, it will cache it for the next time the client checks in. However, if disaster strikes, it is possible an attention ping will be lost. | |||
The Placeholder Server is TRANSIENT. Pings that have not been delivered after a configurable time (likely 36 hours) will be discarded. | |||
The Placeholder Server is NONLINEAR. The order of pings through a channel is irrelevant and nonsequential. The client can tell that there is something that needs attention by the presence of the ping, not the contents of it. Normally, however, the value in the ping will be different from the previous value, to optimize for duplicate delivery. However, this is handled by the Application Server and is not guaranteed. | |||
The Placeholder Server is NONACCUMULATIVE. If two pings come in for the same channel while the client is disconnected, only one of those pings will eventually be delivered. No guarantee is made as to which it is (see NONLINEAR). | |||
The Placeholder Server is OPAQUE. Only the user will have knowledge of the UAID. The Application Server will be pushing data to an endpoint that does not allow them to divine information about a user beyond the specific endpoint channel. | |||
===Why "PlaceHolder Server"?=== | ===Why "PlaceHolder Server"?=== | ||