The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: into a compiled VB.net DLL Class


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

Re Debug messages


  • Subject: Re Debug messages
  • From: Kevin Hawkins
  • Date: Mon, 10 Nov 2003 15:10:00 +0000

I while back I was thinking that we should have a xAP based error
notification using xAP messages - a sort of schema for sending out
diagnostic / debugging /error messages such that a central application
could
log or monitor them. Maybe an opportunity for a central application to
create logging for components maintained in one file (divided into sections
)from many sources.

Perhaps two schemas...

Class=xAP.Error
Class=xAP.Debug

And within each perhaps three levels... possibly the block names should be
identical though with just the class names different.

Error.info
Error.warning
Error.critical Fatal ??

Debug.info
Debug.warning
Debug.critical

Or alternatively put the severity into the block

xAP.error
{
severity=critical
......

All info can be provided within the block with perhaps a description and
details on your specific logfile location

}
debug.warning
{
description=Bad UID encountered
detail=A UID of FF212300 with a source address of
acme.lightcontroller.lounge:centrelight was received
logfile=errorlog.txt
path=c:\xAP\MyApp\logs
}

Any thoughts ?? Gives a way to see real time problems and also to
manage the many different log locations that people will be using..

K







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.