PUBLIC MARKS with tag api

By following the REST style, I would have saved myself either A) having to alter my iOS code and resubmit to the store, or B) time spent researching alternate caching methods and implementing them in Rails. As it stands, my partially-RESTful API is going to cost me (and possibly the client) more time before we can call the project finished.

spire.io provides, as its foundation, a simple REST API. As such, the first thing you do is some discovery to get all the URLs you need to get started.

It's funny how you don't hear so much about service mashups these days, despite their undeniable coolness. I'll assert that it's because developing for Web data in the browser is bloody hard work, especially when there are NxN arbitrary API mappings to know.

With NodeTree we seek a hybrid of these two techniques. Callbacks can be set for virtually every stage of processing, but what is returned is the (possibly incomplete) object being processed. Nodes which have been fully processed can be removed from the tree in processing to save memory and the user can even specify an alternative class to create child nodes of an element. The goal is a clean, Pythonic API usable for the most basic to the most advanced XML processing.

ql.io – a declarative, evented, data-retrieval and aggregation gateway for HTTP APIs. Through ql.io, we want to help application developers increase engineering clock speed and improve end user experience. ql.io can reduce the number of lines of code required to call multiple HTTP APIs while simultaneously bringing down network latency and bandwidth usage in certain use cases.

Computers don’t care about API design. Convenient serialization formats, sane parameter names, and a RESTful interface mean nothing to a robot.  These aspects of an API are not meant for a machine, they’re meant for you – the developer.  APIs should be for human beings first and computers second.

REST URI relative to

But the W3C saw, or was made to see, the writing on the wall and built a set of standard APIs into HTML5 for just this case and most modern browsers have picked it up. The draft for the spec is http://dev.w3.org/geo/api/spec-source.html if you want to read it through or need further info. The API is pretty marvelously simple. This implementation changes the URL to return latitude and longitude when they are available, which we can use in our Django view. Plus, the same code works on mobile devices (at least the iOS ones I carry) with no changes.