[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re Debug messages
- Subject: Re: Re Debug messages
- From: Michael McSharry
- Date: Wed, 10 Mar 2004 03:38:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<DIV><FONT face="Arial" size="2">I'm not
understanding the context of the logfile in the proposed schema.
Is the purpose to notifiy other XAP app's that a log file exists and it can
be retrieved via a UNC file system reference? If this is the
case, then what is a typical application?</FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV><FONT face="Arial" size="2">I have an
Writelog XAP executable that implements a schema consisting of a log
message where the log message contains three fields. One a
timestamp, one a type/classification field, and the third a message
body.. The Writelog application logs the record along with the
source id from the header to a database. The schema is defined in
the draft Homeseer XAP document. The intention is that a cental
record of all XAP node logs are maintained and can be queried by other XAP
apps that want some type of slice through the
database.</FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV><FONT face="Arial" size="2">I
generally believe that the log and error schema should be relatively
free-form. The definition of buckets for types of messages
presupposes an eventual use for this information, however this use has not
been defined so there is no good basis for any type of
categorization. That is why in the Writelog application the
"type" field is free-form. This allows any application
to send what it feels has some significance for logging and
debugging. An application that is later developed to
manage errors, debug, or other log information will be developed based upon
the context of the data that is being managed. Future
applications will likely have square pegs and the definition of round holes
for these pegs will result in a constrained
implementation.</FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV><FONT face="Arial" size="2">For any
given application a convention can be established such that the content of
the "type" field can specify debug at various criticalilty
levels, or that resources are low, or interface power is off, or whatever
is appropriate for that application.</FONT></DIV>
<DIV> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE>
<DIV><B>From:</B> <A title="lists@xxxxxxx"
href="mailto:lists@xxxxxxx";>Stuart
Booth</A> </DIV>
<DIV><B>To:</B> <A
title="xAP_developer@xxxxxxx" href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A>
</DIV>
<DIV><B>Sent:</B> Tuesday, March 09, 2004 2:32
PM</DIV>
<DIV><B>Subject:</B> Re: [xAP_developer] Re Debug
messages</DIV>
<DIV></DIV><TT>On Tue, 09 Mar 2004 22:07:54 +0000, Stuart
Booth<<A href="mailto:lists@xxxxxxx";>lists@xxxxxxx</A>>
wrote:>Class = xAP.Debug>>debug>{>severity={info, warning,
critical, fatal}>description={summary}>detail={longer detail
message}>logfile=>path=>}1. Drop path and combine it into a single
entry, logfile? True, thisis a file relative to the source of the message
and won't always beapplicable e.g. to devices without any storage
capabilities. Or itcould use a UNC pathname.2. Added Category, a string
field that can be used to group debugmessages together.3. Perhaps move the
log file items to a separate block as this meansmultiple debug messages can
be transmitted in the one block, but alllogged to the same file? Or maybe
they go to separate files so thatisn't appropriate? Perhaps an overriding
log file block e.g.Debug.Log{File=<path to log file on device>}This
applies to the entir
e message unless the individual itemspecifies a separate entry.Way more
complicated than is perhaps required.S-- Stuart Booth
<stuart@xxxxxxx>xAPFramework.net - a xAP software development
framework for .net<A href="http://www.xapautomation.org/";>http://www.xapautomation.org/</A>
<A href="http://www.xapframework.net/";>http://www.xapframework.net/</A></TT>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|