Ahh, see how fast that was implemented! :)
thanks for the help. RTFM eh?
So, in fact, when Analog identifies which browser strings go with which browser
summary options, isn't this something we can add into the configuration? Or, does
this need to be programmed into the source code?
For instance, is there, or can there be a definition file that has all the browser
strings, and then listed next to it the category they fit into for the summary report?
This could give customization for people who have abnormal browser strings on their
websites, like the WAP stuff.
sean.
----- Original Message -----
From: "Jeremy Wadsack" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 10, 2000 11:40 AM
Subject: Re: [analog-help] analog using WAP ... a few examples.
>
>
> "Sean D. Ackley" wrote:
>
> > If a browser comes in that is not recognized, that Analog simply just display the
>actual browser information that is displayed, and calculate hits based on that new
>data?
>
> It does. That's called the Browser Report.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
