4 ms·
> saving it for every HTTP request is still a boon I'm questioning the measurability of this, though. Smells like premature optimization. You could be right, b
by bajsejohannes 13y ago
> saving it for every HTTP request is still a boon
I'm questioning the measurability of this, though. Smells like premature optimization. You could be right, but I'd like to at least measure it before we go about changing one of the fundamental protocols on the internet.
Last time I read raw HTTP was when writing a script to automate some stuff on a web page. I specifically did not want the browser's headers and behaviors. I had a bug which only happened from my script, and raw HTTP helped me track it down. I could have used wireshark, but I am much faster in vim for a simple task like that.
- peterwwillis 13y agoHTTP has existed for over 20 years. We've had some time to look at it. It has been measured. As a comparison to your scripting story, you would use Wget or Curl or LWP::UserAgent or a thousand other things to automate HTTP requests. One function call to do what you did manually. To find bugs you would use an HTTP fuzzer like Skipfish to automate the process. If you think somehow your manual process was faster, I say to you, teach a man to fish... (I automate things in web pages for a living, and I only use tools like Firebug and LWP)