The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Re Debug messages


  • Subject: Re: Re Debug messages
  • From: Stuart Booth
  • Date: Tue, 09 Mar 2004 22:32:00 +0000

On Tue, 09 Mar 2004 22:07:54 +0000, Stuart Booth
<<a
href="/group/xAP_developer/post?postID=tumZbxgDSwGHObPhkNrwk4i-LymbeWpp3Iiaa_V2gwFcS4DGroIhba4PV4Av673Jfy_6J7UBx652h4ZseFaO">lists@x...</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, this
is a file relative to the source of the message and won't always be
applicable e.g. to devices without any storage capabilities. Or it
could use a UNC pathname.

2. Added Category, a string field that can be used to group debug
messages together.

3. Perhaps move the log file items to a separate block as this means
multiple debug messages can be transmitted in the one block, but all
logged to the same file? Or maybe they go to separate files so that
isn't appropriate? Perhaps an overriding log file block e.g.

Debug.Log
{
File=<path to log file on device>
}

This applies to the entire message unless the individual item
specifies a separate entry.

Way more complicated than is perhaps required.

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=0MGx4kz6jP2kE8Soy7QmFTOWBez6OTk9R1y613aLuZfdg-s3grLM5338g64KoLLg-X06yWMw840Z3wKL91GZ">stuart@x...</a>>
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>





xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.