What is the need for ‘discoverability’ in a REST API when the clients are not advanced enough to make use of it anyway?
The various talks I have watched and tutorials I scanned on REST seem to stress something called ‘discoverability’. To my limited understanding, the term seems to mean that a client should be able to go to http://URL – and automatically get a list of things it can do.
Are there strategies for discovering REST services using HATEOAS?
When building a REST service with the HATEOAS constraint, it’s very easy to advertise the existence of resources through linking. You make a GET to the root of my site and I respond with the root document listing all the first-tier resources:
Are there strategies for discovering REST services using HATEOAS?
When building a REST service with the HATEOAS constraint, it’s very easy to advertise the existence of resources through linking. You make a GET to the root of my site and I respond with the root document listing all the first-tier resources:
Are there strategies for discovering REST services using HATEOAS?
When building a REST service with the HATEOAS constraint, it’s very easy to advertise the existence of resources through linking. You make a GET to the root of my site and I respond with the root document listing all the first-tier resources:
Link relation values and REL attribute – edited
In REST, do we always use link relation values to convey semantics/role of a linked resource?
Link relation values and REL attribute – edited
In REST, do we always use link relation values to convey semantics/role of a linked resource?
Link relation values and REL attribute – edited
In REST, do we always use link relation values to convey semantics/role of a linked resource?
How to communicate side effects in a RESTful API on the server to the client?
I have been thinking a lot about Hypermedia REST-APIs for the last couple of weeks. One thing I am not quite sure about is how I want to model side effects on the server side.
How to communicate side effects in a RESTful API on the server to the client?
I have been thinking a lot about Hypermedia REST-APIs for the last couple of weeks. One thing I am not quite sure about is how I want to model side effects on the server side.
Defining user operations on application/collection+json response?
I’m fairly new to Collection+JSON. I have a bunch of questions regarding Collection+JSON and user operations.