Jeremy: Thanks for your very helpful response to my original questions. A couple follow-up comments mentioned beneath your points below.
>> >> Gnuth Beagly wrote: >> >> 1) [5.03/docs/compout.html 2nd section, 2nd paragraph] This >> paragraph states that the 2nd field of the CRO contains >> information regarding the remaining columns. From the CRO >> reports I have generated, I've noticed that there are more >> fields than defined by the characters w/in the second field. > >> For example, in the line "D|RP|330|192|2001|08|20" RP says we >> can expext 'number of requests' and 'percentage of bytes' >> (two fields) though we have two fields then a date occupying >> 3 fields. In the line: >> "r|lRbD|1|1527|0.00|2001|09|15|00|02|/images/c.gif", >> we have level, number of requests, percentage of bytes, date, >> but the final field, directory, is not mentioned. > >Jeremy Wadsack wrote: > >All reports also include the final field that is the data item for >each row in the report. In the Request Report, you have to have the >each requested item, no? And in the Daily Report the date that the >requests are totalled for? > Yes, but wouldn't it be helpful (from a generic parsing standpoint) to have a character in the second field tell you what to expect in the final field? If this were the case, the parser wouldn't have to have any special knowledge about what to expect for each report, other than what is described in the meta-data in the second field. In this way, new reports could be added without having to do much (if any?) modification to the parser. >> >> Gnuth Beagly wrote: >> >> Is there somewhere w/in the documentation that defines the >> format of each of the different reports? I was able to >> determine the sytax of 21 of the 44 CRO reports by >> examining my sample data, but was not able to determine >> the remaining 23. > >Jeremy Wadsack wrote: > >I'm pretty sure they all follow the same format. Each row >defines the columns for the row and adds one of more fields >for the data item in that row. Columns can take up more >than one field when they are of a date/time type. Date/time >columns (or data) will never be more than 5 fields and >always uses only as many as needed to define the data. > >The only tricky ones are some of the new time reports which >have interesting syntax to uniquely define the date. > Understood, but again, IMHO, trickery could be avoided if the meta-data in the second column contained information on how the date is described. > >BTW, you might want to look at Report Magic >(http://www.reportmagic.org/) to see how CRO is put into use. >The source is open, so you might be able to glean more >understanding of the format from there too. > I will definitely take a look. Thanks for the reference. >Also, if you want I can send you a CRO file that contains >almost every possible field, data, or item that Analog >could put in there. > This would be very helpful, if you could, please zip it and email it to me. Thanks so much! Your thoughts have been extremely helpful. Sincerely, Gnuth Beagley Make a difference, help support the relief efforts in the U.S. http://clubs.lycos.com/live/events/september11.asp +------------------------------------------------------------------------ | 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/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
