AffableSpatula

10 ms·

61.
by AffableSpatula 14y ago
I have no idea why you would conclude that from that sentence. HTML allows browsers, the same way that HAL allows generic libraries. I'm struggling to understand why this is controversial, there are already 16+ examples of generic HAL libra
62.
by AffableSpatula 14y ago
That is one of the benefits that relates to documentation, which is the part of your comment I was responding too. The larger goal of hal+json is to establish some conventions for linking that allow the development of generic tools for doin
63.
by AffableSpatula 14y ago
Link header parsers are far less ubiquitous than json, and Link headers aren't very good for use cases like representing links that come from items in a collection, there are also issues relating to the maximum feasible size for HTTP header
64.
by AffableSpatula 14y ago
it is an example of a discoverable API with discoverable documentation though, which is what you were asking for I think.. maybe not?
65.
by AffableSpatula 14y ago
Your applicaiton's link relations should be URLs. This means that you can expose each bit of documentation for each rel at their URL. So every time you see a link in a hal+json document, you can follow the _rel's_ URL, and fetch the documen
66.
by AffableSpatula 14y ago
I wrote the spec for application/hal+json that got compared to WS-star , here's where I'm coming from: JSON doesn’t have links. Establishing some basic conventions for that makes complete sense. Defining those conventions is called a spec.
67.
by AffableSpatula 14y ago
nothing specifically. it's an attempt to articulate why making hypermedia APIs the default is a good idea for Rails, in terms that someone like DHH can't just dismiss as "wankery".
68.
by AffableSpatula 14y ago
Because rails is used for building APIs, linking is a good practice, and there's no need to reinvent the linking/embedding wheel every time you create an API. Rails has API defaults which should include sensible linking defaults we can buil
69.
Hypermedia APIs on Rails(blog.stateless.co)
39 points by AffableSpatula 14y ago|18 comments
70.
by AffableSpatula 14y ago
How much overlap do you think your company has with Sustaination ( http://sustaination.co ) ?
71.
by AffableSpatula 14y ago
That begs the question: if you weren't sure what was meant by the terms, why did you assert that they were "all part of science"?
72.
by AffableSpatula 14y ago
Is it better to classify a rabbit by its meat or by its fur? It depends what you want to do with it.
73.
by AffableSpatula 14y ago
Are you sure? As far as I know, none of those have testable explanations.
74.
by AffableSpatula 14y ago
Consciousness, experience, spontaneity, 'the present moment'.. There's a very good book on this called "The Wisdom Of Insecurity" by Alan Watts. It's very short and definitely worth a read if this question interests you.
75.
by AffableSpatula 14y ago
Consciousness/experience.
76.
Show HN: SendGrid for Webhooks(webgun.io)
1 points by AffableSpatula 14y ago|0 comments
77.
by AffableSpatula 14y ago
The link in the OP didn't seem to work, here it is again: http://webgun.io/articles/templated-webhooks
78.
Show HN: Templated Webhooks
3 points by AffableSpatula 14y ago|1 comments
79.
by AffableSpatula 14y ago
browser vendors should be pressured to up their game with regards to web caching. The cacheability of HTTP is the majority of its value as a network protocol and browsers - the defacto HTTP client - just aren't pulling their weight in this
80.
by AffableSpatula 14y ago
there's a gem called roar that's been around for a while for producing hypermedia in ruby. there's also a roar-rails gem specifically for integration with rails.
81.
by AffableSpatula 14y ago
No, not unethical, just plain idiotic. But illegally watching a free TV station at the cost of another country's tax payers is definitely unethical.
82.
by AffableSpatula 14y ago
I'd like to see this happen just so that British taxes aren't being spent providing free coverage to people in other countries.
83.
by AffableSpatula 14y ago
fwiw hal+json has documentation built in (arguably better than HTML does) and its browsable, here's an example API: http://haltalk.herokuapp.com/
84.
by AffableSpatula 14y ago
the interface you establish is the ultimate form of communication with the people behind the clients. You can't force people to read/obey documentation (no matter how pretty or up-to-date it is), but they are obliged (naturally) to follow t
85.
by AffableSpatula 14y ago
"I also didn’t mention the whole REST/RPC/Hypstermedia debate since I consider it being an implementation detail and a totally orthogonal discussion." with respect to the author this article is well intentioned but it is (in my opinion) fun
86.
by AffableSpatula 14y ago
The people taking this action are in charge of how the content should be presented here. You can always vote with your feet.
87.
by AffableSpatula 14y ago
:) already working on a browser: https://github.com/mikekelly/hal-browser very rough demo here: http://hal-shop.heroku.com/hal_browser.html
88.
by AffableSpatula 14y ago
Already exists: https://github.com/s3u/headers.js There are problems with using Link headers, I think you will find less friction in practice by treating links as 'proper data' and putting them in the content body using a media type like
89.
by AffableSpatula 14y ago
Yes I'm loathe to change this. Some have even suggested removing a prefix altogether since underscores are 'not ruby-like'. Hopefully it holds up even though this choice might not be to everyone's taste?
90.
by AffableSpatula 14y ago
Personally I prefer HAL's model because it is couched in web terminology, i.e: - Resources - Resource state - Links hal+json results in more uniform representations, which makes it easier to write generic client + server client libraries fo

More ›