- Where Developers Learn, Share, & Build Careers
I have been following these tutorials well and should say that they are great tutorials!
I'm just confused about the full concept of Zend_Rest abstract methods. In examples, you can only see
remove index post delete
Although these functions are understood, I am trying to explain whether the entire architecture is limited to those abstract methods only. I am thinking about the use case where a consumer wants to use an API to update specific fields, which contains user tables, or other cases where the consumer wants to update the activity table. Business logic of these two tables is included in a Reciprocity API controller. I have to solve this problem by creating specific updates / post method for each table, and to determine which fields are updating This type of implementation is consistent with REST, and if so, how can you move forward in post, beyond, seamlessly?
REST supports hierarchical relationships for architectural resources, and your resources in any way Are not bound by Can your user have a sub-source in the resource? Credentials ???? Which is a map for the user name and password fields in your user table, so that you can make a put request on 'domain' user / wwwuserId} / credentials. You will create one controller and apply it, user is credentials, and update logic will be in action.
You have to work in routing for this, though.
Comments
Post a Comment