3 ms·

Yeah, I'm not sure how using a route table precludes having "an API". You can still have controllers and actions with fairly arbitrary names. More to the point,

Yeah, I'm not sure how using a route table precludes having "an API". You can still have controllers and actions with fairly arbitrary names. More to the point, there is no reason why a DAL-style API can't do things like "activate this user". Just let them CREATE new UserActivation objects.

mmatants 12y ago
I think "activateUser" seems more semantic than "UserActivation/create" - that's just Kingdom of Nouns again.
- ollysb 12y ago
  That seems incredibly easy to represent as a patch patch /users/1 { active: true } or as patch for json patch /users/1 { "replace": "/active", "value": true }