Changes

===HTTP Standardization===

===HTTP Standardization===

IETF initiated the standardization of HTTP standards on the latter part of 1994 which was strongly supported by [[W3C]].<ref>[http://www.w3.org/Protocols/Activity.html#role HTTP Activity Statement]</ref> In 1996, Tim Berners-Lee together with Roy Fielding and Henrik Frystyk Nielsen published the RFC 1945, the first IETF Informational Document for HTTP/1.0.<ref>[http://www.ietf.org/rfc/rfc1945.txt  

IETF initiated the standardization of HTTP standards on the latter part of 1994 which was strongly supported by [[W3C]].<ref>[http://www.w3.org/Protocols/Activity.html#role HTTP Activity Statement]</ref> In 1996, Tim Berners-Lee together with Roy Fielding and Henrik Frystyk Nielsen published the RFC 1945, the first IETF Informational Document for HTTP/1.0.<ref>[http://www.ietf.org/rfc/rfc1945.txt  

Hypertext Transfer Protocol -- HTTP/1.0]</ref> Experimental implementations on HTTP 1.1 was conducted by a group of computer scientists within Libwww, the W3C protocol library and Jigsaw, W3C's Web server. The scientists discovered errors as well as the full potential of the protocol.<ref>[http://www.w3.org/Protocols/Activity.html HTTP Activity Statement]</ref> A proposed IETF standard, RFC 2068 was subsequently published in 1997. <ref>[http://tools.ietf.org/html/rfc2068 Hypertext Transfer Protocol -- HTTP/1.1]</ref>  

Hypertext Transfer Protocol -- HTTP/1.0]</ref> Computer scientists working on HTTP 1.0 discovered flaws on the performance of the protocol. Based on the performance analysis prepared by Simon Espero of W3C, HTTP spends more there is a delay in transferring data  and it has a bad interaction with TCP. A frequent round trip delays was discovered due to connection establishment and a slow start performance was also observed in both directions for short duration connections. The protocol also demonstrates heavy latency penalties because of mismatch of typical access profiles with a single request per transaction model. In addition, HTTP/1.0 requires busy servers to dedicate resources to be able to maintain TIME_WAIT information for large numbers of closed connections.<ref>[http://www.w3.org/Protocols/HTTP/1.0/HTTPPerformance.html Analysis of HTTP Performance problems]</ref>  

RFC 2616 is the current IETF draft standard for HTTP/1.1 which was approved by the Internet Engineering Steering Group ([[IESG]]) on July 7, 1999.<ref>[ http://tools.ietf.org/html/rfc2616 REF 2616 Hypertext Transfer Protocol -- HTTP/1.1]</ref>

Despite the problems discovered with HTTP 1.0, computer scientists from W3C acknowledged the full potential of the protocol and started experimental implementations on HTTP 1.1. Experiments were held within Libwww, the W3C protocol library and Jigsaw, W3C's Web serve.<ref>[http://www.w3.org/Protocols/Activity.html HTTP Activity Statement]</ref> Subsequently in 1997, a proposed IETF standard, RFC 2068 was submitted to the IETF describing the specifications for HTTP/1.1. <ref>[http://tools.ietf.org/html/rfc2068 Hypertext Transfer Protocol -- HTTP/1.1]</ref>

On July 7, 1999, RFC 2616 was approved by the Internet Engineering Steering Group ([[IESG]]), as the current IETF draft standard for HTTP/1.1 <ref>[ http://tools.ietf.org/html/rfc2616 REF 2616 Hypertext Transfer Protocol -- HTTP/1.1]</ref>

==HTTP Working Group==

==HTTP Working Group==