Good day,
As proposed, the real time statistics will induce even more server load time.
If a page is already tracked, the "config.asp" and "class.asp" files are already #included. Doing another include of these 2 files to accomodate the statistics display, will more likely result in variables and classes definitions collisions, on top of a longer server load time in case the collisions are not detected right away.
For the people having their site hosted on II5 and up, perhaps the use of the Server.Excute() would be appropriate to get the stats, but with IIS4, I doubt it would work as shown. Two realtimestats pages will be required, one of which will have the "config" and "class" include if the stats are displayed on a non-tracked page.
Also, some of the displayed stats may not be as "Real Time" as claimed :
1) If the page on which the stats are displayed is not actually tracked, the stats will be off, no question about that.
2) On a tracked page, if the stats are computed before the actual page details are stored in the tracker, the stats will be off too.
For instance, you want to display the online users in the upper part of the page, but the call to the tracker "track.asp", is further down the page, the stats will be off by one hit.
My 2 cents of analysis for today.
Regards.