Events in the networking world don’t usually garner all that much attention from developers. But Cisco is hoping that developers are paying attention to both OpenStack, an emerging standard for managing IT infrastructure in cloud computing platforms, and Project Open Daylight, an open source implementation of a software-defined networking controller that Cisco supports.
One of the most fascinating, yet frustrating, aspects of anything to do with APIs is how rapidly the technology that serves as the foundation for the programmable web evolves. That dynamic volatility was in full view last week at the API Strategy and Practice conference in New York in the form of Daniel Jacobson, director of API engineering at Netflix.
I was lucky enough to attend the API Strategy and Practice Conference this week in NYC and was struck by the wide diversity of attendees. Sure, I expected to see the young guns heading up the industry’s hot new companies, but US Postal Service? Walgreens? AT&T? Target? An even bigger surprise was how relevant and interesting all of the discussions were. But it was obvious there is still the same old gap between the enterprise and the start-up that we have come to expect. For as long as I’ve been in the industry, the difference has always been around governance and process vs rapid innovation.
The World Wide Web Consortium (W3C), an international community that develops web standards, has announced the launch of the new “Automotive and Web Platform Business Group” which will create web technology specifications for the automotive industry starting with a Vehicle Data API Specification.
In the not too distant future unified communications will be a feature embedded in almost every new Web application, which from a developer perspective means that most end users are going to soon view most existing applications as nothing short of being antiquated.The W3C is currently working out the details of a WebRTC specification that essentially puts support for a real-time communication engine directly in the browser.
Remember when Mark Zuckerberg blamed the problematic old Facebook mobile app–dubbed “freakishly slow” by some–on “betting too much on HTML 5?” So does backend-as-a-service (BAAS) provider Sencha, and to rebut Zuckerberg’s assertion that using HTML5 was “one of [Facebook's] biggest mistakes,” Sencha built its own mobile webapp, Fastbook, to demonstrate that HTML5 is ready for prime time.
Partnering with a storage vendor may not be the first thing that comes to mind for most developers, but EMC is looking to changd some hearts and minds about the strategic role storage plays in application development.
The Internet runs on standards. Without standards, we wouldn’t have the Domain Name System (DNS) which resolves hostnames to Internet Protocol (IP) addresses, or the HyperText Transfer Protocol (HTTP) which served up this very web page. Even web service APIs, which can vary wildly depending on the back-end service, depend on standards like XML and JSON to make third-party development possible. And now, the W3C is jumping into the fray with a Working Draft for a general webapp Push API.
While just about everybody would agree that the “Internet of Things” within the context of machine-to-machine (M2M) applications is one of the next big things on the Web, turning that vision into reality has been problematic because of the lack of standards.
The debate over RSS never seems to end. 2011 kicked off with a widely read post predicting the decreasing influence of RSS in 2010. There have been responses from Fred Wilson and GigaOM that argue it is still relevant today. We believe that it continues to be a solid mechanism for web sites to aggregate data from multiple sources, as displayed by the 121 RSS APIs in our directory. In this post, we’ll look at RSS beyond blog syndication.