June 16, 2015
Single purpose API
Related Articles (247)
AudioBoo brings the familiar tape-recorder type interface to the web with all the fixings. Take your audio recording, add a picture, a location, put it in a social context, throw in popularity ratings and you have AudioBoo. The simplicity and social aspects of this service make a great platform for podcasters while providing another avenue of media discovery for users. But it's new and still changing. If you're feeling like an adventurous explorer, ready for twists, turns and surprises, jump on in to the AudioBoo API.
Real-time and the real-time web continue to be a hot topic of conversation but is the term "real-time" getting used correctly? When we talk about real-time technology are we truly describing what the technology is delivering or is it being used and abused as just another marketing buzz word? Can we class any of the current technology solutions as truly real-time and can other solutions be defined in any other way? Is it too late to save "real-time" or will it forever be lost to marketing?
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?