JaroslavTulach at 06:12, 29 July 2018 - 2018-07-29 06:12:29

←Older revision Revision as of 06:12, 29 July 2018
Line 1: Line 1:
-
[[wikipedia:REST|REST]] allows people to use their browser or even command line tool like ''curl'' to control the internet. Designing [[REST]] [[API]] is not covered in [[TheAPIBook]] as [[NetBeans]] IDE cannot (yet) be controlled from a browser.
+
[[wikipedia:REST|REST]] allows people to use their browser or even command line tool like ''curl'' to control the internet.
 +
 
 +
 
 +
[[REST]] has grown way stronger in the [[TenYears|last decade]]. When [[TheAPIBook]] was written, the term [[API]] was still reserved to all [[APITypes|types of API]] ([[Protocols]], [[FilesLayout]], [[Dependencies]], [[CLI]], and of course [[signature]]s). The [[REST]] was just one of the [[APITypes|types]]. I realized things has changed in 2014 when I received a question: How does the ''API economy'' impacts the [[APIDesign]]? At that moment it was clear, the term [[API]] has been kidnapped by the [[REST]] guys. When regular people hear [[API]] they first and foremost envision web services! That is upside down, as network communication is just a part of [[the Art of Building Modern Software]], but the expectations have shifted and one has to live with that.

JaroslavTulach: New page: REST allows people to use their browser or even command line tool like ''curl'' to control the internet. Designing REST API is not covered in TheAPIBook as [... - 2010-11-11 08:55:03

New page: REST allows people to use their browser or even command line tool like ''curl'' to control the internet. Designing REST API is not covered in TheAPIBook as [...

New page

[[wikipedia:REST|REST]] allows people to use their browser or even command line tool like ''curl'' to control the internet. Designing [[REST]] [[API]] is not covered in [[TheAPIBook]] as [[NetBeans]] IDE cannot (yet) be controlled from a browser.