I think it would be a nice addition to list Page Views by Page Title. For example, when I get a dynamic page generated from an Access file, I just get the link with something like "?key=92" added to the end. Of course, I could just look up the records in my database and match them, or keep a list on hand, but when the database contains over 1,100 entries and growing, it would be a lot easier and faster if there was also an option where I could see the page title instead.
Page views listed by Page Title
Hi,
Not to sound like a broken record, but this is a feature I have planned for version 2. I think this would be handy for static pages as well.
Regards,
~Chad
Page views listed by Page Title
Good day,
Perhaps my knowledge of the ASP capabilities, including scripting, is not as sharp as I thought it was.
Chad, how do you plan to get to that piece of information ?
Unless I'm mistaken, this information is accessible directly from Javascript, however I don't know for sure how it could be accessed via JScript or VBScript, unless you do an extensive round of gymnastic. ;)
At first glance, it looks that this feature will be something limited to the Javascript method, pretty much like the screen resolution and many other browser related specifications.
Regards.
Page views listed by Page Title
There are a few ways to do this. With javascript logging, there is the document.title property, as you mention. In the administrative tools, you could use http requests to grab the url and parse the page title (assuming you had access to the components to do this, many web hosts do). Finally, it could be typed in manually for each page in an administrative tool as a last resort.
Regards,
~Chad
Page views listed by Page Title
Chad,
Personnally, I think the javascript "document.title" is more likely the more appropriate way to go, although the javscript tracking has its limitations.
On the other hand, I'm just hoping you're not planning to invoke XMLHTTP or read the file via FileScriptingObjects each time a page is accessed, otherwise I can almost see a performance hit occuring.
Just for the sake of the discussion, may I suggest the following :
) As with the automatic removal of aged records, a refresh of the titles could be performed at per a pre-established interval.
- mt_ScriptNames : Lookup table for the site's scripts
- pl_scriptname : Guess what ? [:p]
- pl_scripttitle : Rather obvious 8)
- pl_scriptlastupdte : Timestamp of the last script update
- ... : Any other usefull stuff related to the page.
If the last update is within the pre-established time interval, then the title is extracted from the script and the corresponding entry is updated automatically. Otherwise, no update occurs. I guess FileScriptingObject would be more appropriate, since using a GET with XMLHTTP would result with an extra unnecessary entry in the log.
Knowing that the process doesn't require client's interaction, asynchronous remote scripting would be a perfect candidate for that type of work; when the update is due up, an application variable is set indicating that the update is ongoing, (preventing collisions), and initiated asynchronously, which simply means that the update will take place behind the scene while the user can continue browsing the site at his how pace.
Doing it asynchronously has the very interesting advantage of being able to update a fairly substantial amount of entries, and the user will not even have to wait for the completion, therefore the site size wouldn't be a real issue in that case.
Since the "Last Modified" timestamp is available via FSO or Javascript, regardless of the method used for the tracker, the titles will always be up to date.
Any comments/suggestions/ideas ?
Regards.
Page views listed by Page Title
I would like to see page load time improve so I would probably not want to perform file system access or http requests during logging.
The only problem with using FSO to get page titles is that if the site is not hosted on the same box, this presents a problem. You would also need to know the directory that the site is located in to get this information. Also, if there were virtual directories setup with different file paths, this could present additional complications.
~Chad
Page views listed by Page Title
Good day,
Indeed there are different ways to get to a given result, and each one of these ways have their respective pros and cons.
Accomodating all possible setups isn't something that can be achieved easily, if at all, therefore a clear mention of a given approach limits, pros and cons, would be more than appropriate, preventing false assumptions/expectations.
There is no perfect way to do the things, nor is there any perfect way to get to a piece of information, so all potential / implemented possibilities should be clealy identified along with their respective limitations and/or requirements, whenever applicable.
Regards.