Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Restful Web Services

The slide will introduce to you the basic knowledge about REST. After viewing the slide, you can research depper about REST supported in specified language you are using (C#, PHP, Java, ...)
by

on 6 July 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Restful Web Services

Resources
Verbs
Output
- JSON
- XML
- CSV...
Pluralization
Example:
http://localhost/api/users/
http://localhost/api/users/1/Orders
URI
- At least 1 URI for each public resource
- Makes sense and adequately
- Predictable, hierarchical structure

Example:
http://localhost/Users
http://localhost/Users/2/Orders
http://localhost/Users/2/Orders/3
GET
- Retrieve the resource
- Example:
GET http://localhost/api/users
PUT
- Update a resource
- Example:
PUT http://localhost/api/users/1
POST
- Add new resource
- Example:
POST http://localhost/users
DELETE
- Delete an resource
- Example:
PATCH
- Partial update resource
- Example:
What is REST?
- Representational State Transfer

- Architecture style for designing networked applications
JSON
- Use request header:
accept: application/json

- Use query string:
GET http://localhost/api/users?format=json

- Use file extension:
GET http://localhost/api/users.json
Constraints
 Client-Server
 Uniform Interface
 Stateless
 Cacheable
 Layered System
 Code on Demand

DELETE http://localhost/api/users/1
PATCH http://localhost/api/users/2
s
GOAL
Scalability of component interactions
Generality of interfaces
Independent deployment of components
Full transcript