Would it make sense to have a resource that simply performs REST calls? get would be GET, set would be POST, and test wouldn't be implemented (so synthesized).
For the returned payload, it would be useful to have access to the headers, so the response would be wrapped in a response object that includes header, body, etc... rather than the raw response from the REST call.
Idempotency can't be enforced other than trying a get before set.
Summary of the new feature / enhancement
Would it make sense to have a resource that simply performs REST calls?
getwould beGET,setwould bePOST, andtestwouldn't be implemented (so synthesized).Proposed technical implementation details (optional)
The resource would need these properties:
For the returned payload, it would be useful to have access to the headers, so the response would be wrapped in a response object that includes header, body, etc... rather than the raw response from the REST call.
Idempotency can't be enforced other than trying a
getbeforeset.