Basic Introduction About API Web Service
0 likes574 views
REST was designed by Roy Fielding to define constraints for web architectures and ensure protocol extensions would not violate the core principles that made the web successful. REST uses a stateless, client-server, uniform interface approach and relies on HTTP for data transfer, utilizing methods like GET, POST, PUT, DELETE. Fielding used REST principles to design HTTP 1.1 and URIs.
1 of 10
Downloaded 20 times
More Related Content
What's hot (20)
PPTX
Misconfigured CORS, Why being secure isn't getting easier. AppSec USA 2016Evan J Johnson (Not a CISSP)PDF
Preparing your web services for Android and your Android app for web services...Droidcon Eastern EuropeMisconfigured CORS, Why being secure isn't getting easier. AppSec USA 2016Evan J Johnson (Not a CISSP)
Preparing your web services for Android and your Android app for web services...Droidcon Eastern Europe
Viewers also liked (20)
Ad
Similar to Basic Introduction About API Web Service (20)
Ad
More from Hiraq Citra M (9)
Recently uploaded (20)
Basic Introduction About API Web Service
- 1. API - WEB SERVICE ~ BASIC
- 3. Entitas provider consumer / client DATA
- 4. Transactions REQUEST + RESPONSE = DATA
- 5. Web Services - Types ● wsdl ● soap ● rest
- 6. REST REST has been applied to describe desired web architecture, to identify existing problems, to compare alternative solutions, and to ensure that protocol extensions would not violate the core constraints that make the Web successful. Fielding used REST to design HTTP 1.1 and Uniform Resource Identifiers (URI). http://en.wikipedia.org/wiki/Representational_state_transfer REST => DATA DELIVERED VIA HTTP
- 7. HTTP ● OPTIONS ● PUT ● DELETE ● PATCH ● GET ● POST ● TRACE ● CONNECT ● HEAD
- 8. HTTP - GET (example)
- 9. HTTP - POST (example)
- 10. END You have to learn the rules of the game. And then you have to play better than anyone else.