Re: [Specifications] [client-interface] Suggestion for browser-like client API

The sample cli is written in pseudocode. It makes use of a hypothetical hydra object which has certain property accessors and methods. Notably:

- setLocation: the equivalent of entering a url in the address bar
- representation: access to the header and body received after requesting the most recent resource, i.e. the current application state
- controls: access to hypermedia affordances in the current representation
- execute: make use of a given hypermedia affordance to transition to another representation, i.e. application state.

The interaction with the hypothetical hydra client uses these accessors and methods by means of the pseudo language. A real hydra object would of course need accessors and methods for a real language.

The findEntrypoint method is not necessary, as stated by the hydra spec.

The current representation is usually the result of an interaction with a server resource identified by a URI (unless the interaction was fulfilled from a local cache). E.g. a GET for a URI may result in a response which is a representation of the requested resource.


-- 
GitHub Notification of comment by dschulten
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/111#issuecomment-289275615 using your GitHub account

Received on Sunday, 26 March 2017 11:37:37 UTC