Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
AffableSpatula
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
91.
▲
by
AffableSpatula
14y ago
fwiw, I used xml2rfc for this, it inserts all the boilerplate for you http://xml.resource.org/
92.
▲
by
AffableSpatula
14y ago
In my opinion, Link Headers are not a good option as the primary hypermedia of your API. They are useful for adding links to responses with a Content-Type that is not capable of expressing a link, and they are useful for protocols ( http://
93.
▲
by
AffableSpatula
14y ago
point well made, thanks. I will probably incorporate this in the next version of the draft.
94.
▲
Internet-Draft: JSON Hypertext Application Language (lean format for linking)
(raw.github.com)
17 points
by
AffableSpatula
14y ago
|
24 comments
95.
▲
by
AffableSpatula
14y ago
No, WebIntents are just plain Links: <intent action=" http://webintents.org/share type="image/ " href="share.html" disposition="window|inline" /> <link rel=" http://webintents.org/share type="image/ " href="
96.
▲
The Waka Protocol (pdf slide deck)
(tools.ietf.org)
8 points
by
AffableSpatula
15y ago
|
0 comments
97.
▲
Upgrading WebHooks To Be More Useful
(blog.stateless.co)
2 points
by
AffableSpatula
15y ago
|
0 comments
98.
▲
by
AffableSpatula
15y ago
Would've been fine as a comment on the thread posted 3 minutes earlier about the same news: http://news.ycombinator.com/item?id=3695407
99.
▲
Traffic Cop: 'Super lightweight messaging system'
(github.com)
4 points
by
AffableSpatula
15y ago
|
0 comments
100.
▲
by
AffableSpatula
15y ago
I did some research on this a couple of years ago - the aim was to come up with a mechanism that extended HTTP so any existing caching infrastructure could pick it up and implement it. I wrote up a summary of the research here: http://rest
101.
▲
by
AffableSpatula
15y ago
can you really get 'much' simpler than REST already is? it's only 5 constraints. Why is it significant that the web evolved between 1995 and when Fielding defined REST? To most people, the paper is well-reasoned and REST is observable in th
102.
▲
by
AffableSpatula
15y ago
honestly, I'm not sure what you were trying to say. Yes it is a post-rational analysis of the web.. yes the web was not 'designed' - it evolved.. but do I think, because it evolved, that means it doesn't/can't have an underlying architectur
103.
▲
by
AffableSpatula
15y ago
are you saying you are not convinced that the dissertation holds water? afaict, REST is (right now) the undisputed way to interpret the web's architecture.
104.
▲
by
AffableSpatula
15y ago
Producing RESTful applications is more of an art than a science. There are two key objectives to bear in mind when designing a web app to be RESTful: - your app should produce client/server interactions which complement the semantics of HTT
105.
▲
by
AffableSpatula
15y ago
REST is not a scam, it's THE term for the underlying architectural style of the web. Your straw-man interpretation is a scam. The crappy silverlight app is badly designed and the performance issues you were seeing can be optimised away triv
106.
▲
An Introduction to the Tao: Skillful Living
(majc.openwisdom.org)
1 points
by
AffableSpatula
15y ago
|
0 comments
107.
▲
Hyperlinks with JSON
(blog.stateless.co)
1 points
by
AffableSpatula
15y ago
|
0 comments
108.
▲
by
AffableSpatula
15y ago
Be awesome if this had a jsgi and/or connect interface to drop in HTTP middleware components for given routes.. is this on your roadmap?
109.
▲
How I made my OSX user experience not suck
(blog.stateless.co)
2 points
by
AffableSpatula
15y ago
|
0 comments
110.
▲
by
AffableSpatula
15y ago
HAL already incorporates standards for the URI template spec and the CURIE syntax. It's also going to be rejigged to incorporate terminology direct from the Web Linking RFC. The above being the case, it doesn't seem as if HAL is re-inventin
111.
▲
by
AffableSpatula
15y ago
Yep, it definitely should be making reference to the IANA registry (will likely do this by referencing Web Linking RFC5988). The point here was not to necessarily invent new capabilities, but to take a unique position in its design and brin
112.
▲
by
AffableSpatula
15y ago
Might be worth exploring if re-using stuff like XLink makes sense and is within keeping of the objective to keep things simple. Probably better to discuss that on the google group than here, feel free to join and raise it there. At the mome
113.
▲
by
AffableSpatula
15y ago
The intention with hal was to keep things as simple as possible. RDF (and its related media types) don't do a very good job of this, in my opinion. I think the real-world usage is a good indicator of whether RDF is appropriate for most peop
114.
▲
by
AffableSpatula
15y ago
yeah.. sorry about that ;) Sketched it out about a year ago, the design has changed a tiny bit since then but it's basically the same http://bit.ly/acgCyY
115.
▲
HAL is a lean hypermedia type for your RESTful APIs
(stateless.co)
12 points
by
AffableSpatula
15y ago
|
18 comments
116.
▲
by
AffableSpatula
15y ago
Your app should already have fallbacks for 'certain unavailable resources'. I don't think this does clutter the HTTP, in fact the proposal even provides an alternative to the one single addition it does make to HTTP. I'm not clear on the ot
117.
▲
by
AffableSpatula
15y ago
That's a decent point about clearing the cache - it should be distinct from flushing assets indicated for offline use. That distinction could be drawn by determining whether or not each asset was served with stale-if-error.
118.
▲
by
AffableSpatula
15y ago
There's not a fatal error there, afaik. I didn't detail how to deal with un-accessed files because the solution seemed trivial: when your application boots up, make sure it prefetches all required assets (i.e. warms the cache) by making aja
119.
▲
by
AffableSpatula
15y ago
Yep, agreed, some apps could easily generate more than 10mb in a couple of weeks. It's definitely an issue. Users could take all their data with them following this proposal since, provided the Cache-Storage was high enough, data that is pu
120.
▲
by
AffableSpatula
15y ago
many apps could get by using a combination of LocalStorage (for storing un-synced data generated by the user offline) and this caching strategy (for storing all of the synced data locally). It's not SQL, but it likely covers a decent amount
More ›