ly entered into the appropriate log file. If the value were set to 100, then the first 100 messages would be collected in the cache and be logged in the corresponding text-based log file at the same time. For example, when the user seeks to print 50 messages at a time, once the cache is full with the first 50 messages then it will print or write the 50 messages in the log file and then continue to store the next 50 messages in the cache. Specifying some cache file allowance avoids frequent writing to the log file which can improve application performance and also reduce the incidence of conflict when the log file is being written to from several sources. FileCount: This is the maximum number of log files that can be written at any time. LogLevel: When a particular level is specified for messages to be recorded, the messages with levels lower than or equal to the given value will be recorded. The LogLevel parameter allows the user to choose how much detail in the mes- sages is to be logged, and module-specific log levels can be set. The levels are as follows: -LogLevel = 1 indicates summary or important messages -LogLevel = 2 indicates intermediate or frequently generated log messages -LogLevel = 3 indicates verbose or error messages. The levels cascade, so that if a level of 3 is given, all the messages with levels 1,: and 3 are written. LogsDirectory: This is the name of the directory in which both system and server related log files are to be stored. The user can create sub-directories specific to a particular module under the logs directory. useTimeStamp: Setting this to true appends to the log message a timestamp of when the action or event occurred. Logging: This parameter enables/disables the logging of messages. That is, mes- sages are recorded if and only if Logging is set to true. Key name: The Key name differentiates modules and logs module-specific mes- sages. The Key name is also used to identify the type of message, such as output message or error message. DisplayName The display name is a module-spe