Slashdot Mirror


Why IE Is So Fast ... Sometimes

safrit writes "Finally the scoop on how IE "cheats" a little to up its performance! Do RFCs mean nothing anymore? What's next, Riots in the streets, dogs and cats living together, mass hysteria! From the blog story: 'Internet Explorer on Windows always seems either to run impossibly fast (page requests are fulfilled almost before the mouse button has returned to its original unclicked position), or ridiculously slow...' Now read to see why..."

3 of 887 comments (clear)

  1. Post this Blog by 1stflight · · Score: 0, Redundant

    Can anyone post this blog, it's either down or Slashdotted

  2. sounds like T/TCP by Anonymous Coward · · Score: 0, Redundant

    TCP has a standard for this, called T/TCP.

    Its also perfectly legal to send data on the SYN, the SYN gets acked after all.

    So what's the big deal?

  3. Re:Cut n Paste by Sunda666 · · Score: 2, Redundant

    Hmmm this smells bad to me.

    I am no TCP guru, but this looks a bit odd. From the text I understand they say IE establish a connection without sending a SYN packet....
    I may be wrong, but this is totally impossible to do over TCP/IP. SYN is required, in order to establish a new TCP sequence and inform the server that it is a *NEW* connection, not something related to an old one.
    If all this guy claims is true, the screwup is below IIS and IE. It is in the windows TCP/IP stack. And I am really puzzled how they manage to do connection tracking this way. Ah, and for sure, if it really works this way, it can't be called TCP/IP.

    Ofcourse if it just opens the connection in a normal SYN way and keeps it open for all the HTTP requests, nothing is wrong. These are new features of HTTP/1.1 called keep-alive and pipelining, and even Mozilla supports them (check preferences/advanced/HTTP networking).

    cheers

    --


    ``If a program can't rewrite its own code, what good is it?'' - Mel