web-api-style
web-api-style copied to clipboard
Consider Server-Push requirement
This could be optional, but is a key trend for the next wave of APIs as led by Twitter API, WebSocket and HTTP 2.0 specification efforts: http://tools.ietf.org/html/draft-ietf-httpbis-http2-02
I think "Real-Time" is very vague. restrictions on latency might be easier to quantify. this may also be better handled at the protocol selection level, not the architectural style level.
We could find a better name. HTTP 2.0 talks about "server push", HTML 5 has SSE (server-sent events), Twitter has a streaming API:
- http://en.wikipedia.org/wiki/Push_technology
- https://dev.twitter.com/docs/streaming-apis
The idea is to ensure that actual Web APIs following our style properly take into the growing need to have more frequent and 'instantaneous' communication through web APIs.
Renamed issue from "Real-time" to "Server-Push" requirement