i don’t like that you cannot link to individual slides. not RESTful at all.
Tag: REST
Amazon fails at REST
Designing in side-effects to GET requests is a fundamental mistake of web development that people who don’t understand the web/http tend to make. It’s less common now than it used to be, but I’m suprised to see it in a web API from one the biggest web properties and doubly surprised to see it called “REST”.
what is it with amazons infatuation with SOAP? how can they be a web company yet develop such lousy “API”s?
Long Bets Apologia
the architecture of the www now informs everything: REST style everywherre, search-centric data stores, languages that scale out instead of up, making information survivable in the face of data loss and dissonance between systems
ETag Algorithm
What you want to do is compute the ETag based on the underlying data resources that actually drive the page creation; the input to that process, not its output.
Restful Services for Geospatial Information
ron lake:
The OGC is now actively considering the expression of its web services such as WFS, WRS, WMS and WCS using a REST model.
woo! good work, sean.
Crawl Before You Walk
It is striking that it is only in its 5th year of existence that a framework for building web applications is considering allowing bookmarking and might even use the HTTP GET method where applicable.
AJAX and automation
For these 2 reasons — the transparency of the HTTP pipeline, and the accessibility of the JavaScript object model — I think that AJAX is inherently more automatable than conventional GUI apps ever have been.
the view source qualities of RESTy interfaces are only slightly impacted by JSON / XMLHTTP, imho. more problematic: the js obfuscation.
General-purpose intermediation
It ought to be trivial to attach an observer and/or filter to HTTP pipelines. Among other things, it could shovel data into a search engine so that I could instantly recall a remembered transaction by search term, by date, or by site.
stefano’s pipelines coming to HTTP. this enabled jon to reverse engineer a gmail api
They can’t hear you
the typical corporate technologist hasn’t considered REST and decided against it, they haven’t even heard the term. Ditto RelaxNG, Atom, and everything else that makes the Web work and makes working with the Web easy
soo true
Computational REST
REpresentational State Transfer (REST) guided the creation and expansion of the modern web. The reformations introduced with REST permitted the web to achieve its goal as an internet-scale distributed hypermedia system. Yet, the web has now seen the introduction of a vast sea of shared and interdependent services. Despite the expressive power of REST, these new services have not consistently realized the anticipated benefits from REST. In order to better understand the unwritten axioms necessary to realize these anticipated benefits, we survey the history and evolution of the web’s infrastructure – including Apache HTTP Server, Firefox, and Squid. We also recount our experiences developing such systems and the challenges we faced due to the lack of thorough design guidance. We then critically examine these new services from the vast sea – including Service-oriented architectures, RESTful Web Services, and AJAX – to glean previously undocumented lessons about how these services are constructed and why they do not consistently realize the benefits expected from REST. Based on this, this dissertation presents a new architectural style called Computational REST (CREST). This style recasts the web from a model where content is the fundamental measure of exchange to a model where computational exchange is the primary mechanism. This crucial observation keys a number of new axioms and constraints that provide new ways of thinking about the construction of web applications. We show that this new style pinpoints, in many cases, the root cause of the apparent dissonance between style and implementation in critical portions of the web’s infrastructure. CREST also explains emerging web architectures (such as mashups) and points to novel computational structure. Furthermore, CREST provides the necessary design guidance to create new web applications which have not been seen before. These applications are characterized by the presence of recombinant services which rely upon fine-grained computational exchange to permit rapid evolution.
justin has some big plans for his dissertation