1 / 4

REST and BLISS

REST and BLISS. Jonathan Rosenberg Keith Griffin Cisco. REST and BLISS. If we go this way, what do we need to do? “Framework” Model for the data we want to manipulate Users, device, identity General structure of the URI Lightweight – not really a framework at all

alice
Download Presentation

REST and BLISS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. REST and BLISS Jonathan Rosenberg Keith Griffin Cisco

  2. REST and BLISS • If we go this way, what do we need to do? • “Framework” • Model for the data we want to manipulate • Users, device, identity • General structure of the URI • Lightweight – not really a framework at all • Specific BLISS resources • Call forwarding numbers and preferences • Keep it minimal – only what needs be manipulated by an automata

  3. Example Data Model root users devices devicename username feature • Highly abstracted fromunderlying DB • Each resource has XMLspecific to that resource featuredata GET users/bob/cfna/forwardto PUT devices/bobsphone/cfna/forwardto

  4. Proposal • Don’t boil the ocean • Don’t define a RAI-wide REST framework please! • Define a basic data model for feature data – the scope of BLISS • Proposed document structure • Single framework doc • Each BLISS document needing feature data defines its own specific elements and XML • Possibly an event package for HTTP resource changes – but this is a secondary objective

More Related