I don’t like writing client apps that use APIs. Writing HTTP client code to talk to APIs is verbose, repetitive, chatty and slow. This is in addition to addressing latency and bandwidth constraints and core functionality of the client app – such as building a snappy UI or supporting some other business use case.
For a soon-to-open sourced nodejs based platform that I have been working on since June this year, I needed a way to send some optional telemetry data back to the browser without mixing it with the real data that the client code is interested in. The first thing I looked at was socket.io. Socket.io’s claim […]
A while ago I showed how chatty some well-known apps are on my iPhone. But this issue is neither new nor unique to apps on phones and similar devices. Efficient data retrieval from distributed/decentralized servers is a well-recognized problem in distributed computing. For instance, in the abstract of his November 1994 paper A Note on […]
I just caught up with the recent reactions to the “hashbang” episode. Of all the reactions, I’m most intrigued by Ben Cherry‘s post. Ben’s point is that the Web has been slowly transforming from “traditional web sites” into “desktop-class applications” served via HTTP, and that “the hashbang is in the unfortunate position of being the […]
HTTP pipelining is often suggested as a way to dramatically improve page load times, or to solve multi-GET use cases for RESTful applications. Whether pipelining can achieve the intended effect or not truly depends on what gets pipelined and how the server implements pipelining. When using pipelining, a HTTP client sends idempotent HTTP requests (such […]
O’Reilly will be offering the ebook version of the RESTful Web Services Cookbook on sale tomorrow (Jan 19, 2011). Here is the scoop I just received from O’Reilly. Save 60% – Top 25 of 2010 Best of Ebook Deal of the Day – http://post.oreilly.com/rd/9z1ztpijtp7meklse9bq1u34nnvf1fdmc1n0battp2g For one day only, you can save 60% on our best […]