George Reese
![]() |
The REST API Design Handbook
2 editions
—
published
2012
—
|
|
![]() |
MySQL Pocket Reference
12 editions
—
published
2003
—
|
|
![]() |
Cloud Application Architectures: Building Applications and Infrastructure in the Cloud (Theory in Practice
13 editions
—
published
2009
—
|
|
![]() |
Database Programming with JDBC & Java: Developing Multi-Tier Applications (Java
7 editions
—
published
1997
—
|
|
![]() |
Java Database Best Practices
7 editions
—
published
2003
—
|
|
![]() |
Mysql. Leksykon Kieszonkowy. II Wydanie
—
published
2012
|
|
![]() |
MySQL kurz & gut
by
2 editions
—
published
2007
—
|
|
![]() |
George Reese
|
|
![]() |
Java Enterprise Architecture
|
|
![]() |
MySQL. Leksykon Kieszonkowy. II Wydanie
2 editions
—
published
2007
—
|
|
“For now, let’s just say that if your API is re-defining the HTTP verbs or if it is assigning new meanings to HTTP status codes or making up its own status codes, it is not RESTful.”
― The REST API Design Handbook
― The REST API Design Handbook
“In fact, the biggest misconception is that you can call your API RESTful if its delivering XML or JSON over HTTP. And that misconception and the resulting proliferation of horrible APIs is likely the source of RESTafarian irritation with the application of the term “RESTful” in an API context. But let’s be brutally honest. Most interactive systems don’t follow this model either.”
― The REST API Design Handbook
― The REST API Design Handbook
“Someone consuming an API will definitely notice when the provider of that API is diverging from RESTful principles and it will seriously complicate that consumer’s life.”
― The REST API Design Handbook
― The REST API Design Handbook
Is this you? Let us know. If not, help out and invite George to Goodreads.