W3C's work on HTTP Next Generation (HTTP-NG) has been managed as part of W3C's Architecture Domain.
Activity statements provide a managerial overview of W3C's work in this area. They provide information about what W3C is actively doing in a particular area and how we believe this will benefit the Web community. You will also be able to find a list of accomplishments to date and a summary of where we are headed. The area overview is often a good source of more generic information about the area and the background reading pages can help set the scene and explain any technical concepts in preparation.
Between July '97 and Dec '98, the HTTP-NG Activity explored the future development of the HTTP protocol. The motivation was the impression that HTTP/1.1 is becoming strained modularity wise as well as performance wise. The HTTP-NG Activity produced a number of proposals that successfully addressed these issues, which were presented to W3C members and at an IETF meeting in Dec. 98. At the moment, W3C does not plan any follow-up work on HTTP-NG.
The work on HTTP-NG has been done at W3C by Henrik Frystyk Nielsen, Jim Gettys and Daniel Veillard who worked with other researchers from a number of companies and organizations. All the documents produced by the Protocol Design Group are already available as either W3C Technical Reports or IETF Internet Drafts.
At the IETF in Orlando, December 1998, we presented the initial work described in the Internet Draft " HTTP-NG Overview: Problem Statement, Requirements, and Solution Outline" along with the following IETF Internet Drafts:
While there was interest in the Project, the general feeling was that it was too early to bring it to IETF and that we needed to provide a plan for how to get where are today to where we would like to be. One of the arguments that we got was that people were just getting used to HTTP/1.1 and saw HTTP-NG as a 'warm-hole' into a very different Web infrastructure than what we have today.
Two results came out of this:
The HTTP-NG Activity has achieved its goals in outlining potential solutions for the future development of HTTP. At this point, W3C does not plan any follow-up activities.
Yves Lafon, W3C
Jim Gettys, Visiting Engineer - Compaq Computer Corporation
Last modified $Date: 2001/06/13 10:09:07 $