rest
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| rest [2018/02/28 16:02] – [compare REST vs just some HTTP based interface] skipidar | rest [2023/06/06 09:53] (current) – skipidar | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| Es werden Methoden übergeben: | Es werden Methoden übergeben: | ||
| - | | |GET | POST | PUT | DELETE| PATCH| | + | | | GET | POST | PUT | DELETE| PATCH| |
| - | |Safe|x| | | | | | + | |Safe | x | | |
| - | |Idempotent|x|x| |x| | | + | |Idempotent| |
| Line 14: | Line 14: | ||
| A good describtion is here: \\ | A good describtion is here: \\ | ||
| - | http://www.se.uni-hannover.de/pub/ | + | https://restfulapi.net/idempotent-rest-apis/ |
| Line 29: | Line 29: | ||
| - | ==== What makes REST different from SOA or HTTP-based interfaces | + | ==== What makes REST architecture mature? 4 steps ==== |
| https:// | https:// | ||
| Line 61: | Line 61: | ||
| </ | </ | ||
| + | |||
| + | |||
| + | === Glossary === | ||
| + | | Compound Documents | < | ||
| + | To reduce the number of HTTP requests, servers MAY allow responses that include related resources along with the requested primary resources. Such responses are called “compound documents”. | ||
| + | https:// | ||
| + | </ | ||
| + | |Sparse Fieldsets| A client MAY request that an endpoint return only specific fields in the response on a per-type basis by including a fields[TYPE] parameter. < | ||
| Line 214: | Line 222: | ||
| ==== HAL - Hypertext Applicaiton Language ==== | ==== HAL - Hypertext Applicaiton Language ==== | ||
| + | |||
| + | **REST** is a concept of application architecture. Its multiple maturity states are defined above: Stack of POX, Ressource, Verbs etc. | ||
| + | |||
| **HATEOAS** is a concept of application architecture. It defines the way in which application clients interact with the server, by navigating hypermedia links they find inside resource models returned by the server. | **HATEOAS** is a concept of application architecture. It defines the way in which application clients interact with the server, by navigating hypermedia links they find inside resource models returned by the server. | ||
| Line 221: | Line 232: | ||
| **HAL** is one of such standards. It is a specific format of resource presentation, | **HAL** is one of such standards. It is a specific format of resource presentation, | ||
| + | |||
| + | |||
| + | * HAL Introduction: | ||
| + | * HAL browser: http:// | ||
| ===== REST API Example ===== | ===== REST API Example ===== | ||
| Line 327: | Line 342: | ||
| </ | </ | ||
| + | |||
| + | |||
| + | == CURIES == | ||
| + | Cut URI - an approach to reduce the long URLs | ||
| + | |||
| + | < | ||
| + | GET http: // | ||
| + | data{ | ||
| + | id: 1, | ||
| + | type: characters, | ||
| + | attributes{ | ||
| + | name: " | ||
| + | size: " | ||
| + | race: " | ||
| + | }, | ||
| + | curies{ | ||
| + | { | ||
| + | name: " | ||
| + | href: " | ||
| + | }, | ||
| + | links{ | ||
| + | self: " | ||
| + | prev: " | ||
| + | next: " | ||
| + | } | ||
| + | } | ||
| + | } | ||
| + | </ | ||
| + | |||
rest.1519833736.txt.gz · Last modified: (external edit)
