Now that both HTTP extensions and HTTP/1.1 are stable specifications (RFC2616 at that time), W3C
has closed the HTTP Activity.
An effort to revise HTTP/1.1 started in 2006, which led to the creation of the IETF httpbis
Working Group. Work completed with the publication of RFC 723X (See below)
An extension mechanism for HTTP designed to address the tension
between private agreement and public specification and to accommodate
extension of HTTP clients and servers by software components
W3C offers the Jigsaw server written in Java and
the libwww client API - both released with a full
set of HTTP/1.1 functionality including caching and persistent connections.
Please see the W3C open source contributions for
more details.
The HTTP/1.1 performance
paper explains the experiments in detail, and was recently
submitted for publication. This work shows how you can gain as much as
a factor of 10 in number of packets and 2 in times of speed by using
HTTP/1.1 pipelining. Earliest results were presented at the IETF meeting in San Jose,
December 1996, and more complete results at the W3C Advisory Committee Meeting
in England in January.
This presentation gives a good overview of new features. It will be
updated occasionally as it is presented. The presentation is also
available for Microsoft
PowerPoint
There are several mailing lists that you are welcome to use. As several of
them are very high volume then please check out the archives first to see if
the topic that you want to bring up in fact already has been discussed. As we
try to make as much progress on HTTP as possible it is very important that we
can stay focused - even on open mailing lists!
This is a W3C mailing list dedicated to promote HTTP/1.1
implementation, to gain sufficient experience among W3C Members to
support the specification, and ease
development of HTTP/1.1 software and applications. The list is only
accessible to W3C members.
This is the primary public mailing list for technical
discussion among those developing World Wide Web software. It
is explicitly intended for the collaborative design of new systems,
software, protocols, and documentation which may be useful to the WWW
developer community. General questions from non-developers should go
one of the many newsgroups.
The Internet Engineering Task Force
(IETF) is the protocol engineering and development arm of the Internet. The
IETF is a large open international community of network designers, operators,
vendors, and researchers concerned with the evolution of the Internet
architecture and the smooth operation of the Internet. It is open to any
interested individual.
Also check out the IETF meeting page for
the latest information. We keep a small list of notes from previous HTTP wg
meetings at various IETF meetings:
The Internet Research Task Force
(IRTF) is a composed of a number of focused, long-term, small Research
Groups. These groups work on topics related to Internet protocols,
applications, architecture and technology.
The Internet Architecture Board
(IAB) is a body of the Internet Society responsible for overall
architectural considerations in the Internet.
The Internet Society (ISOC) is a
non-governmental International organization for global cooperation and
coordination for the Internet and its internetworking technologies and
applications.
The Internet Assigned Numbers
Authority (IANA) is the central coordinator for the assignment of
unique parameter values for Internet protocols
Internet Message Access Protocol
(IMAP) is a method of accessing electronic mail or bulletin board
messages that are kept on a (possibly shared) mail server
Next Generation Internet (NGI)
Initiative. On October 10, 1996, President Clinton and Vice President
Gore announced their commitment to the Next Generation Internet (NGI)
Initiative, based upon strong research and development programs across
Federal agencies.
