XLF: Legacy Log Problems

[Don Park]

>It could be useful to indicate the variety of log file types. I assume that
>HTPP logs will be the favorite. [Example: I spend my time grepping the VSMS
>server logs to see what percentage of JUMBO2 downloads break - by using the
>byte count. ] Are you anticipating the elementTypes will be as detailed as
><ByteCount> or more general like <Transaction>? [I assume the latter, with
>additional means of qualification through attributes.]


I think many of legacy log format problems originated with
over-anticipation.  Each log producers should determine their own level of
details which could change depending on situations.  FTP server could avoid
writing out the <bytecount> element until it encounters failure situations.

For example, normal FTP entry could look like this:

<ftp:get file="/pub/xlf-spec.doc">
    <ftp:start when="07/07/1998 12:24:48"/>
    ...
    <ftp:end when="07/07/1998 12:30:00" error="12">
        <xlf:bytecount>19989</xlf:bytecount>
    </ftp:end>
</ftp:get>

[ Above example actually points to one of the problems of using XML.
Elements can not be nested too deep when there is more than one log producer
because start and end tags could get mixed up unless the log server prevents
the element from being written out until the end tag is received. ]

Regards,

Don





xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)