|
|
|
|
|
by ianterrell
5464 days ago
|
|
Before he even discusses his individual points the author gives his definition of "bad," and the reason the other approaches are "bad." From the introduction: > Let's talk about a few cases where either REST or HTTP (which is clearly RESTful in its design) solves a common web development problem. > so they make up a partial solution that solves their given case but doesn't jive well with the way that everything else works |
|