> yes I know if all web APIs were all hypermedia we'd only need one clientSDK per language, and that assuming we had a standard for hypermedia. But I
I have actually taken that approach in my current work - exposing a case
The idea is to have a generic HTTP (C#) client that works with the REST
Let me give an example ...
The generic client is "Ramone" (see
The SDK defines "const" values for link relations:
}The SDK defines classes that represent the wire format:
}The SDK defines media codecs (see
transforming between the wire format and the SDK classes. Ramone has
built-in support for JSON and XML (and HTML) transformations, so often this
is not required.
The service is assumed to present a service document at a well known URL
From here the generic client just "follows its nose" using hyper media and
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.