Jerome Louvel
Jerome Louvel
Explain the difference between the API contract, its implementation and runtime aspects including actual data/service exposed. Include diagram.
From this section: http://roy.gbiv.com/pubs/dissertation/web_arch_domain.htm - Low Entry-barrier - Extensibility - Distributed Hypermedia - Internet-scale - - Anarchic Scalability - - Independent Deployment
Suggested by Robert Brewer: I would rephrase it to "disconnected operation" and make it a constraint. That constraint plus the cache constraint could lead to _an architecure_ which syncs caches...
Suggested by Robert Brewer
Suggested by Robert Brewer. Under "Custom Interface", it would be very informative to lay out in detail which of the properties are being traded off when selecting explicit versioning. Not...
Similar to chapter 6 in Fielding's dissertation: http://roy.gbiv.com/pubs/dissertation/evaluation.htm - Standardizing the Programmable Web - Web API applied to URI - Web API applied to HTTP (versions 1.1, 2.0) - Web...
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
See latest HTTP 2.0 draft: http://tools.ietf.org/html/draft-ietf-httpbis-http2-02 HTTP 1.1 had focus on: - implementation simplicity - accessibility HTTP 2.0 has focus on: - better application performance - optimized mapping of the...