Re^6: Should I just print my own HTTP headers?

No useful program will ever print out 100,000 HTTP headers on purpose and exit. That'd be like me benchmarking various ways to roll a cigarette--completely useless because I don't smoke.

Obviously not, but it's it's quite likely that the program that prints 1 header will be run 100,000 times. I kind of wish this thread would just die since it keeps costing me experience points, but let me sum up like this: Is "it doesn't take all that long to load" really a good argument to advocate the use of a module? I'm sure CPAN is full of quick loading modules, but why would I use them if I don't need to?

Comment on Re^6: Should I just print my own HTTP headers?

Replies are listed 'Best First'.
Re^7: Should I just print my own HTTP headers? by chromatic (Archbishop) on Apr 11, 2007 at 18:26 UTC
... it's it's quite likely that the program that prints 1 header will be run 100,000 times. Then why not profile the entire program, including network IO, to see if the cost of loading the module is even significant? Is "it doesn't take all that long to load" really a good argument to advocate the use of a module? The real question is "Without actually measuring, is worrying that a module might take too long to load sufficient justification to write my own minimal replacement?"	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.