Timeline for Implementing the command pattern in a RESTful API
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2013 at 4:39 | vote | accept | Mithir | ||
| Jan 25, 2013 at 19:39 | comment | added | Evan Plaice | In this case the URI should represent a transaction where debiting (taking money) and crediting (giving money) are actions done via POST requests. POST is used for both because each time money is moved in either direction it represents a new transaction being created. In your specific case, the transactions are taking place on a cardholder's account so the card's account number is the resource URI. | |
| Jan 25, 2013 at 6:33 | comment | added | Mithir | @EvanPlaice Ok I understand, thanks. I think it's confusing here because Deposit could be thought of as a noun and as a verb... | |
| Jan 25, 2013 at 0:57 | comment | added | Evan Plaice | I would have elaborated in an answer but Gary's answer already covers most/all of what I'd add. I say it's not rest because URIs are only supposed to represent resources (ie not actions). Actions are handled through GET/POST/PUT/DELETE/HEAD. Think of REST as an OOP interface. The goal being to make the API fit the general pattern and decouple it from implementation specific details as possible. | |
| Jan 24, 2013 at 8:23 | comment | added | Mithir | @EvanPlaice care to elaborate on that? that's exactly the question. | |
| Jan 23, 2013 at 18:53 | comment | added | Evan Plaice | Short answer, that's not REST. | |
| Jan 23, 2013 at 15:00 | answer | added | Gary | timeline score: 14 | |
| Jan 23, 2013 at 8:18 | answer | added | Jan Hudec | timeline score: 0 | |
| Jan 23, 2013 at 7:11 | history | asked | Mithir | CC BY-SA 3.0 |