Agreed; REST clients/frameworks should have ways of handling all six of these problems--none of them are specific to a particular API.
If the client lib has an API-specific way of handling "caching", say, then the number of ways of handling "caching" is O(n) in the number of APIs you consume. If you use the REST APIs directly, then the HTTP's standard, debugged, documented caching mechanism is the only one you ever need to know.
Comments
Agreed; REST clients/frameworks should have ways of handling all six of these problems--none of them are specific to a particular API.
If the client lib has an API-specific way of handling "caching", say, then the number of ways of handling "caching" is O(n) in the number of APIs you consume. If you use the REST APIs directly, then the HTTP's standard, debugged, documented caching mechanism is the only one you ever need to know.