-
> It’s inflexible, difficult to implement, difficult to test, with performance and implementation issues. But most importantly, any implementation of REST model is very complex.
> Now to the reader…
-
Responses should use [JSON API](http://jsonapi.org/) instead of whatever homegrown thing we're using now. This shouldn't be too hard, since the API is already pretty RESTful and takes advantage of hyp…
-
Personally, I think it's time to leave the .NET Framework behind.
This project doesn't use anything like WinForms or WPF, so there are no issues there.
However, some of the sample projects are .…
-
Currently Heracles extracts things like operations into a `hypermedia` property. The proposal is to either use `hydra` instead or directly use Hydra terms like `member`.
The reason I don't like hyp…
-
```
What steps will reproduce the problem?
1. make an HTTP request
2. the response body (json or xml) contains some URLs (as common in
REST/Hypermedia api)
3. be able to directly click on the respons…
-
Let's level up for a second.
We talked about just starting with a way to reuse hypermedia libraries across web stacks and clients. So ideally I could use CJ (my library), Uber, HAL, and JSON API with…
-
Spring Data REST is built on top of Spring Data repositories and automatically exposes them as REST resources. It utilizes hypermedia to allow clients to discover the functionality exposed by reposito…
-
This is the thread to discuss use of hypermedia as part of the HSDS v1.x. Now is the time to have this discussion, and discuss the evolution of the project.
I'm suggesting we look at the following …
-
Is support for Hydra already considered?
Hydra Core Vocabulary
A Vocabulary for Hypermedia-Driven Web APIs
http://www.hydra-cg.com/spec/latest/core/
-
Must work on Resthub REST API and clean it if needed:
- relations management
- patching ?
- hypermedia or reference support ?
- Serialization
- Param converters
- ...
partially related to #164, #45