Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente Dernière révision Les deux révisions suivantes | ||
cours:service_oriented_computing_and_web_services:2017-2018:excerpts_from_the_literature_on_web_service_questions_and_answers [2018/04/11 17:35] tigli |
cours:service_oriented_computing_and_web_services:2017-2018:excerpts_from_the_literature_on_web_service_questions_and_answers [2018/04/12 06:24] tigli |
||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
======= hindsight issues about Web Services ======= | ======= hindsight issues about Web Services ======= | ||
- | See [[https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf|Architectural Styles and the Design of Network-based Software Architectures - Ph.D. DISSERTATION of Roy Thomas Fielding, 2000 ]] | ||
- | Why HTTP is not RPC according to Roy Thomas Fielding ? (6.5.2) | + | ** HTTP GET ** |
- | Why HTTP is not a Transport Protocol according to Roy Thomas Fielding (6.5.3) | + | GET: The method GET is used to retrieve/read a representation of a resource and should only be used for that purpose When used only for reading is considered safe (no change on the ressource) and even idempotent (one change ). |
+ | But what are the risks ? | ||
+ | * with an unconstrained use of HTTP/GET | ||
+ | * with the intrinsec limitation of HTTP serveur implementation (develop a C# project to illustrate this limitation) | ||
+ | |||
+ | ** See [[https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf|Architectural Styles and the Design of Network-based Software Architectures - Ph.D. DISSERTATION of Roy Thomas Fielding, 2000 ]] ** | ||
+ | Why HTTP is not RPC according to Roy Thomas Fielding ? (6.5.2) | ||
+ | |||
+ | Why HTTP is not a Transport Protocol according to Roy Thomas Fielding (6.5.3) | ||