Top all-time · #25185
Mike Kelly
Personal blog · restafari.blogspot.comprogrammingweb
Mike Kelly writes A Fundamentalist Restafarian, a personal blog at restafari.blogspot.com about programming and web. Since 2010, 3 different Hacker News readers have linked it 4 times, most often “Linked Cache Invalidation”. The last post was in 2011, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for posts on REST and hypermedia design, including a look at HAL-style JSON hypermedia, HTTP link-header cache invalidation, and resource-oriented controllers and routes.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Mike Kelly talking about REST, HTTP, web and some other stuff too probably.
Most-linked posts?
- Linked Cache Invalidation2 people · 2 mentions · first linked 2010-05-20
What Hacker News says?
The main argument is flexibility and acknowledging what the role of the controller actually is in a resource-oriented application Idea 2 is the way to go because it's resource oriented and you get useful stuff like 405's for free which you don't with the sinatra approach. Please don't remove routing. Having routes is important - it makes the code more descriptive and easier to follow. All a route needs to do is map…
Comment linking /2010/04/restful-php-applications-despite-zend.html
on “Rethinking Rails 3 Controllers and Routes - PeepCode Blog”Submitted Linked Cache Invalidation as a story · 2 points
HN discussionI think it's rare to see JSON HyperMedia data formats in the wild, XML seems the preferred choice due to its use of attributes for metadata annotation. Here's on of the few examples I've found that uses JSON: http://restafari.blogspot.com/2010/10/evolving-hal.html
Comment linking /2010/10/evolving-hal.html
on “Open-source, JavaScript JSON HTML viewer released”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://restafari.blogspot.com/2010/04/link-header-based-inva... Since then Mark Nottingham and myself have written this up as an internet draft: http://tools.ietf.org/html/draft-nottingham-li…
Comment linking /2010/04/link-header-based-invalidation-of.html
on “Show HN: Stash, a graph-based cache for Node.js and Redis”