APIs

TwitterFacebook
Get flash to fully experience Pearltrees
http://www.infoq.com/presentations/Writing-Usable-APIs-in-Practice

Writing Usable APIs in Practice

Daniel Smith details some of the new features prepared for Java 8 by Project Lambda: lambda expressions, default methods, and parallel collections. Daniel Smith Mar 28, 2013 Scott González explains what BrowserStack offers for cross-browser testing, how debugging in BrowserStack works, and how to leverage its API.

The Right End of REST

http://www.zapthink.com/2011/10/09/the-right-end-of-rest/ One of our Licensed ZapThink Architects , Michael Poulin, struggled with our recent ZapFlash , Where is the SOA in REST-Based SOA? In a forum post , Poulin asked: If we have a UI that works with the middle- and back-end resources, do we care if … REST or Web Services are used behind the UI?
http://www.javaplex.com/blog/using-atmosphere-for-comet-websocket-and-rest-web-services/#.TtYKNXP-i8Y What is Comet? Comet is technique to refresh the web browser from server push without refreshing the page. Comet is known by several other names,

Using Atmosphere for comet, websocket and REST Web Services | Java Plex by Java Developers

Nobody Understands REST or HTTP

http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http Since I've posted this, I've refined a few of my positions on things. Everyone learns and grows, and while I still stand by most of what I said, I specifically don't agree that versioning the media type is how to properly version APIs. Hypermedia APIs should not actually use explicit versioning, but I'd rather see a version in the URI with HATEOAS than no HATEOAS and versioned media types. I've been meaning to update this post and write more, but alas, my work on Get some REST has taken priority. I don't have a HN account, so feel free to email me with any thoughts or questions! Furthermore, everything in engineering is ALWAYS a trade-off.

API design for integrating SAAS services - ChargeBee

http://blog.chargebee.com/78993299 We are in the midst of designing the API for our service. Sharing our notes, thoughts and design process based on our experiences in this. API design is a tricky business. The problem being that once users start using them, it is tough to modify the API.

SXSW 2012: The Year of the API

Is this the year of the API? Or is it next year? As we’ve pointed out before, the API universe is expanding . You have a chance now to make sure when thousands of geeks descend upon Austin next March, that this new way of the web is given the billing it deserves. But you have to get moving by September 2. There were over 3,000 potential talks submitted and public votes have a big say in what makes its to the SXSW stages. http://blog.programmableweb.com/2011/08/31/sxsw-2012-the-year-of-the-api/
This table provides a classification of HTTP-based APIs. The classification achieves an explicit differentiation between the various kinds of uses of HTTP and provides a foundation to analyse and describe the system properties induced. Providing distinct names for the API 'styles' overcomes the useless situation where APIs are named 'RESTful' and 'not so RESTful','almost RESTful', or 'unRESTful'. An API either adheres to REST's interface constraints or it does not and if it does not, there is no sense in referring to 'REST' in the API's name. http://www.nordsc.com/ext/classification_of_http_based_apis.html

Classification of HTTP APIs

Microformats vs RDFa vs Microdata « Philip Jägenstedt

http://blog.foolip.org/2009/08/23/microformats-vs-rdfa-vs-microdata/ Warning: The microdata syntax has changed (e.g. item="foo" is now itemscope itemtype="foo" ) since this blog post was written. Don’t copy the examples. I spent last weekend with my good friend Emil sketching a REST-style interface for his graph database Neo4j . One of the output formats we wanted was plain HTML for easy debugging via the browser.

unREST as the new REST?

http://www.infoq.com/news/2011/07/unrest Catherine & Raj have been working in Enterprise Agile transitions in large hardware manufacturers, they share their experiences and advice on leadership and bringing Scrum to hardware teams. Resistance from management is recognized as a bottleneck in agile adoption. When will we reach the tipping point where organizations unshackle themselves from the limitations of command & control? Tiago Garcez Apr 01, 2013 Martin Thompson explores performance testing, how to avoid the common pitfalls, how to profile when the results cause your team to pull a funny face, and what you can do about that funny face.
http://amundsen.com/blog/archives/1101 i've been spending the last several months experimenting w/ a repeatable methodology for expressing business processes as media types for dist-net implementations (aka "the Web"). this blog post is one of a series i've been doing over the last year or so as i attempt to improve upon these patterns and practices. the RESTBucks example the book REST in Practice uses a very effective demonstration app called RESTBucks to illustrate the authors' ideas on how to build RESTful solutions. the book is one of three (along with RESTful Web Services and The RESTful Web Services Cookbook ) i highly recommend for those interested in applying the REST style. i like the 'RiP' book for a number of reasons. one of them is that the problem domain used for the example (RESTbucks) is both simple enough to grasp and complex enough to be non-trivial. IMO, this makes for a great teaching tool when discussing REST, Hypermedia, and dist-net architectures.

amundsen

HAL - Hypertext Application Language

Author: Mike Kelly ( mike@stateless.co ) Dates: 2011-06-13 (Created) 2012-10-22 (Updated) Status: Draft Summary HAL is a format you can use in your API that gives you a simple way of linking. It has two variants, one in JSON and one in XML. The JSON variant of HAL (application/hal+json) has now been published as an internet draft: draft-kelly-json-hal .