In this way, RESTful interaction is driven by hypermedia, rather than out-of-band information. If the API Client wants to manipulate the Table resource it will follow the link to do any operation on that resource.
So if the API Client needs the Table of the Order Resource it will do an GET on that link.
Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. Sign up to join this community Does the update api accept a country object or just a country id. It's also more data that you need to pass around, keep secure, validate and clean-up.
The country object will not be updated, only the reference to the country gets updated? One exception is that if all your clients always have the data in a certain format, then it'll make sense to make it easy for them to pass the data in whatever format/structure they all have and translate to your preference server side.
My preference is country id since we are not updating the country object, but my college think otherwise. The key abstraction of information in REST is a resource.
Them do a POST to create a new Client resource or a PUT to modify an existing one in the Client API URI.; microsoft.support = microsoft.support