Quote:
Originally posted by beepbeep
Hold it there!
It has nothing to do with IIS. It's called "browser caching" and browser does it automaticaly. You can even instruct it to do it every time or never (in "options"), or control it server-side.
...snip...
So it has nothing to do with web-server. M$-bashing is pretty popular "sport", but in this case it's not a culprit.
|
Ummm, two wrong assumptions:
First visits to PP-BBS pages had slowed, that has everything to do with server performance. It is impossible for the browser cache to be relevant to my comment, the server must deliver at least one copy of the data object to the browser before ANY client-side caching can occur. I was talking about the NT file system cache on the server and the lack of control in tuning it for the main use of a server, a long-standing problem since beta copies of NT v3.0 and not greatly changed in the latest renamed flavors of v5 NT.
Identifying deficiencies and better alternatives is not the sport of bashing, it's based on empirical data of identical hardware running identical site pages and measuring delays in the server's ability to deliver content. No opinions or fashion involved.