On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
REpresentational State Transfer • Architectural Style – Many ways to implement • 5 Primary Constraints to be considered “RESTful” – Client / Server – Stateless – Cacheable – Layered System – Uniform Interface
wRESTlingwith thewebwith theweb
Why do we REST? • Client side and Mobile Applications – Apps load fast, data comes after – Local caching • API data access – Allow others to use your data
RESTful Web API • Web service implemented using HTTP and the principles of REST • Clients interact with RESTful servers over HTTP methods – Create (POST) – Read (GET) – Update (PUT)
Services Module (3.x) – Creates URL callback endpoints for integrating external applications – Supports multiple interfaces including REST, XMLRPC, JSON, JSON-RPC, SOAP, AMF, etc.
Services Module (3.x) – Supports Drupal core resources, third party integration is done with modules – Authentication and OAUTH support – Performs a full bootstrap :( – Caching in 7.x-dev YAY! (Issue #1791978)
Services Endpoints Create: POST /[endpoint_path]/[resource] + body Retrieve: GET /[endpoint_path]/[resource]/[resource_id] Update: PUT /[endpoint_path]/[resource]/[resource_id] + body Delete: DELETE /[endpoint_path]/[resource]/[resource_id]
cRESTingtowards the futuretowards the future
Drupal 8: The Promise Land • WSCCI: Web Services and Context Core Initiative – Utilizing Symfony 2 HTTP services – Native RESTful services baked into Core