- From: Dietrich Schulten via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Mar 2017 16:41:21 +0000
- To: public-hydra-logs@w3.org
@lanthaler the original version guided me to believe that the document should not just outline an interface but show a pseudocode application which *makes use* of the hydra client library:
## Retrieve a resource
resource = hydra.download(url)
I see an application there which uses the hydra client, and that approach makes sense because it allows you to think about the interface from the caller's perspective. The PR in all its shortness goes full circle in that it tries to cover all cases where the caller needs to work with server expectations: uri templates, headers and request bodies.
If somebody else would rather write a totally different initial PR and actually tasks himself to do it very soon, let's wait. Otherwise, we could continue with this PR and someone rewrites it so that `hydraClient` is only a starting point and the caller uses a representation abstraction for all further interaction.
Obviously it is not a good mode of operation if everybody tells me they had a very different idea, asking me to bring their idea to life - accompanied by jeers and catcalls ;-) Or at least that is how it felt on my end.
--
GitHub Notification of comment by dschulten
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/111#issuecomment-289830458 using your GitHub account
Received on Tuesday, 28 March 2017 16:41:30 UTC