The Google Dart team has announced Dart SDK 1.3 which improves the performance of asynchronous server-side code to the point that Dart VM is on par with Node.js, the later using another Google technology, the V8 engine.
QUIC (Quick UDP Internet Connections, pronounced 'quick') is a multiplexing transport protocol running over UDP with the main goal to have 0-RTT connectivity overhead.
In a recent blog posting Mark Nottingham, chair of the HTTP/2 Working Group, gives his opinion on 9 things to expect in the next version of the Web standard which is rapidly nearing completion and implementations are starting to appear.
The NodeJS based Koa web application framework has released version 0.2.0. Koa is the successor of the popular Express MVC platform, but relies heavily on newer ES6 constructs. This release is marked as an important one in that that it reaffirms the team’s design choices from the initial 0.1.0 release, solidifying Koa's API for future releases and production use.
The recent Snowden revelations have impacted the IETF HTTP/2 Working Group and how the protocol should handle encryption, i.e., should it be mandated? Mark Nottingham, the Working Group chair, shares his thoughts on the discussions so far and gives a clue as to how he sees it being resolved given information so far. He concludes by asking anyone with an opinion to share it with the Working Group.
Ole Lensmar, creator of SoapUI, has asked whether REST is really appropriate for architectures that require real-time, asynchronous interactions and binary protocols. In his article he discusses these areas and believes that alternative approaches are required.
Twitter has developed and open sourced CocoaSPDY, a framework for OS X (Cocoa) and iOS (Cocoa Touch) based on the implementation they previously contributed to Netty, updating in the same time their iOS application to use SPDY instead of plain HTTP. Twitter has noticed up to 30% decrease in communication latency, the improvement being more noticeable when an “user’s network conditions get worse.“
Amazon has recently added audio support for elastic transcoder that provides an ability to convert media files from one format to another without any depending upon about servers, storage and scalability.
A recent posting on a REST Architects list has prompted Ganesh Prasad to outline some problems that he sees with REST (over HTTP) in terms of more dynamic peer-to-peer environments and how they could be addressed. He suggests some lessons could be learned from Web Services and mentions an Internet Draft specification which he has been working on.
The editors of the HTTP specification have published an initial draft of v2 which is a straight copy of SPDY and will be used as a base for diffs going forward. Many changes are expected to be done like adding new features, removing existing ones, changing the bytes on the wire, etc. A draft ready for test implementations is expected to be published early next year.
IETF has discussed the future of HTTP, and the next version is to be using SPDY as a starting point. There is a controversy though: Microsoft claims SPDY is no better than HTTP/1.1 with all optimizations turned on, while SPDY’s inventor says Microsoft’s tests actually confirm SPDY’s advantage in a real world scenario.
Lori MacVittie has recently posted an article describing why she believes SPDY will gain much wider acceptance in the Web than WebSockets. For her and several others, the differentiating aspect between these protocols is the way in which they use HTTP and SPDY wins because of this.
On behalf of the IETF, Mark Nottingham has recently published a draft of the Home Documents for HTTP APIs specification. Intended for non-browser clients, it provides a way to describe resources available from a particular site as well as possible hints on how to interact with those services.
Google and Microsoft want to improve HTTP with SPDY and Speed+Mobility. This article reviews both proposals outlining what benefits they bring to the much used Internet protocol.
Rackspace's Mark Nottingham, discusses the recent HTTPbis Working Group meeting, clarifications to the HTTP/1.1 specification, and the influence of SPDY on the group that have resulted in a change to its charter enabling them to begin considering HTTP/2.0.