Stephen Turner ([EMAIL PROTECTED]; Friday, September 20, 2002 12:16 PM):
> On Fri, 20 Sep 2002, James Riemermann wrote: >> >> I use the "internal search report" all the time on our >> template/database-driven site to see what people are searching for on our >> site. It occurred to me that all this report is doing is delivering the >> attribute of a given parameter. So, why wouldn't it work to analyze any >> parameter I wanted, rather than just internal searches? >> > Sure. It's deliberate. But maybe the report isn't very well named. I've > never quite known what to call it. Well, I think Internal Search Report is a really good name, considering it works very well for that purpose. It could also be called a CGI Parameter Report or something like that, too. But, as is, only monitoring aggregate parameter counts, it's most useful in a situation like Internal Search. I like James's suggestion of creating a very similar report that breaks down the results in a hierarchy for each parameter given in the config file. That could make a very useful CGI Parameter tracking report. -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/analog-help@lists.isite.net/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
