I'd like somebody to tell me how they've approached the issue using custom member or collection actions for a REST resource, e.g. PUT /users/:id/confirm or PUT /kittens/pet_all
This is obviously a complex task. To properly implement it would be difficult because outside of resourceful routes, there is no assumed contract for the server's request/response type or structure. It sucks, though, when hypothetically all I want to do is pet_all my kittens, regardless of the outcome and must resort to hacking together an ajax request to do so.
Please, think of the kittens...