Slashdot Mirror


HTTP 1.1 approved by W3C and IETF

fabbe writes "The HTTP 1.1 protocol has been approved by the W3C and IETF. CNET article is here. " Both bodies apparently showed ruthless efficiency getting these standards out there... speeds that make even glaciers jealous.

2 of 78 comments (clear)

  1. Doing something PROPERLY takes time. by Anonymous Coward · · Score: 4

    I was watching a show called "Flightpath" on Discovery channel last night and they were showing all sorts of nifty things about the new YF-22 fighter aircraft. This is the new hybrid stealth fighter that is going to replace the F-15 for general figter missions.

    This plane has been under development more or less for the past 19 or 20 years. Although there are 9 or so flight ready versions of this plane which exist TODAY, there will not be any in actual military service for about 5 more years. Some people have described these planes as the most complex machines ever built. They HAVE to work perfectly because if they don't, the pilots will probably be killed and their strategic value will be lessened.

    When much of the software being used today is labelled "mission critical" don't you think it should be well thought out and done PROPERLY as well? Perhaps not 25 years, but don't you find it amazing how stupid is it to spend so much money on software that only partially works?

    The notion of "internet time" is complete and utter BS, invented solely to give software companies excuses for shoddy software and to make "lazy programmers" seem more productive.

  2. HTTP/1.1 performance and other issues... by jg · · Score: 5

    It wasn't quite as glacial as one might think.
    The draft standard was approved in March; the
    RFC issued recently when the RFC editor caught
    up on backlog. The internet drafts have not had
    a significant change for nearly a year. Most
    vendors have been working to the ID's for a long
    time.

    HTTP/1.1 has already been pretty widely deployed:
    this was the approval of the draft standard,
    rather than the proposed standard.

    As to performance stuff, see:
    http://www.w3.org/Protocols/HTTP/Performance/

    As to recovering IP addresses, most clients
    have been sending the host name as part of the
    request using the HOST header for a long while.
    This means you can distinguish different web sites
    without depending on the IP address to distinguish
    them.
    - Jim Gettys
    HTTP/1.1 editor.