Best practice way of Restfully updating multiple Resource types?

You could create a new virtual resource that is responsible for making the changes to the other resources.

You could create a new virtual resource that is responsible for making the changes to the other resources. Resources: User, Account, Deal Account has an attribute, owner (a User) Account has many Deals Deal has an attribute, owner (a User) User has many Deals Want the resource to manage: Changing Account owner Changing Deal owner for all Deals associated with the Account where Deal owner == (old) Account owner Synchronous: URL /account_ownership_update POST: Send the Account to be updated and the new User. Return success/failure Asynchronous: URL /account_ownership_update POST: Send the Account to be updated and the new User.

Return enqueue successful/failed GET: Return the status of the update (pending, running, successful, failed).

Thanks for that fd! That is something we had discussed here but we are very new to REST. It's good to get some feedback that this is a viable option.

Thanks again for info. – Stefg Jul 19 '10 at 13:13.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.