in reply to Random URLs for pages with dynamic content .. better way?
Let me elaborate a little on my post and the reasons for posting it. And, if the consensus is that the query is not appropriate, then let it be withdrawn forthwith with no objections from me.
This site will be visited by 3,000 to 5,000 users simultaneously, and, right now, it serves every shred of information to every request every time ... using the random string in the URL specifically to ensure that no page is ever cached. I regard the “random string in a URL” trick as being unnecessary, given the now-introduced use of Cache-Control and ETag headers. But I wanted to “bounce” that opinion off of the heads of what I calculate would be the most qualified group of colleagues that I know of, anywhere.
I say again ... if anyone feels that the thread is inappropriate to have been posted or approved, then, let the NodeReaper do his solemn duty, without further delay and with my cordial apologies.