As we continue to work on designing and implementing REST APIs for the different services, Josh and I would like to propose guidelines for PUT and POST endpoints. I quickly wrote up a document outlining the proposal. It is on the wiki at:
That sounds about right to me. One question, for what resources do we want to allow PUT, which is basically putting ? For example don’t think we would want to make it possible to put whole requisition objects.
Also important to note about PUT is that it should be idempotent, so sending the same request multiple times should have the same result.
Regards,
Paweł
···
On 15.09.2016 08:59, Chongsun Ahn wrote:
Hey everyone,
As we continue to work on designing and implementing REST APIs for the different services, Josh and I would like to propose guidelines for PUT and POST endpoints. I quickly wrote up a document outlining the proposal. It is on the wiki at:
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlmis-dev@googlegroups.com.
To view this discussion on the web visit [https://groups.google.com/d/msgid/openlmis-dev/E169907E-8C9D-4644-9804-10292DE0DC7F%40villagereach.org](https://groups.google.com/d/msgid/openlmis-dev/E169907E-8C9D-4644-9804-10292DE0DC7F%40villagereach.org?utm_medium=email&utm_source=footer).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
As we continue to work on designing and implementing REST APIs for the different services, Josh and I would like to propose guidelines for PUT and POST endpoints. I quickly wrote up a document outlining the proposal. It is on the wiki at:
In the “resources that have a natural key” scenario, what if you want to edit some of the fields that make up a natural key? E.g. I want to rename a right in the system from “Get Xyz” to “Fetch Xyz”. As you’ve drawn things out, this can’t be done.
That sounds about right to me. One question, for what resources do we want to allow PUT, which is basically putting ? For example don’t think we would want to make it possible to put whole requisition objects.
Also important to note about PUT is that it should be
idempotent, so sending the same request multiple times should have the same result.
Regards,
Paweł
On 15.09.2016 08:59, Chongsun Ahn wrote:
Hey everyone,
As we continue to work on designing and implementing REST APIs for the different services, Josh and I would like to propose guidelines for PUT and POST endpoints. I quickly wrote up a document outlining the proposal. It is on the wiki at:
