HearSay News

Please ensure that all code you are working with complies with logging policies

One of the HearSay config files contains these settings, which you can tune for best results:

HEARSAY_LOG_DUMP_CONSOLE = true

HEARSAY_LOG_DEBUG_LEVEL = FATAL|ERROR|WARN|INFO|DEBUG|TRACE

Besides log messages, no garbage output is allowed

Garbage logging has to be removed before CVS commit

Except for the TRACE level, no intrusion on user-privacy is allowed at other levels

You cannot record typed keys, websites, or any personal information

The following are the log levels given in the order of increasing granularity:

FATAL

HearSayLogger.getInstance( ).fatal(“message”);

The FATAL level designates very severe effor events that will lead the application to abort.

FATAL should NOT be used in case of errors that the application can recover from.

If the log message is used in the try-catch block use this variation of the log command

HearSayLogger.getInstance( ).fatal(“msg”,e);

level: ERROR

command: HearSayLogger.getInstance( ).error("message");

The ERROR level designates error events that might still allow the application to continue running.

If the log message is used in the try-catch block use this variation of the log command

HearSayLogger.getInstance( ).error("msg",e);

level: WARN

command: HearSayLogger.getInstance( ).warn("message");

The WARN level designates potentially harmful situations.

If the log message is used in the try-catch block use this variation of the log command

HearSayLogger.getInstance( ).warn("msg",e);

level: INFO

command: HearSayLogger.getInstance( ).info("message");

The INFO level designates informational messages that highlight the progress of the application at coarse-grained level.

It has to be used occasionally at change of state (e.g.: speech on, context off), on entering a module (e.g.: dialog gen, vmxlSurfer)

level: DEBUG

command: HearSayLogger.getInstance( ).debug("message");

To be used ONLY for research purposes - NOT in development.

level: TRACE

command: HearSayLogger.getInstance( ).trace("message");

The TRACE level designates finer-grained informational events that are most useful to debug an application.  To be put at the beginning and end of each function permanently!  Can be used throughout the code for developmental purposes.

The HearSay project is funded by the National Science Foundation