Issue 2677:  get_capacity_thresholdlist() and set_capacity_thresholdlist()                                                                                                                                          (log_service-ftf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: Should the Log interface define the get_capacity_thresholdlist()
 and set_capacity_thresholdlist() operations? The BasicLog interface
 inherits from Log and yet thresholds are meaningless in the context
 of the BasicLog Why are they defined in Log and not in event and
 notify log? And should BasicLog even bother checking the parameters or
 doing anything?
 

Resolution: resolved , see text below
Revised Text: Resolution: 
Capacity thresholds do have meaning for BasicLogs. What needs to be noted 
is that instead of generating a ThresholdAlarm event, a BasicLog could write 
to stderr or syslog when a capacity alarm threshold has been crossed. 

Revised Text: 
Specification Text 
Section 3.2.4.11: Log Capacity Alarm Threshold 
NOTE: BasicLogs are simple logs that are not aware of events nor are BasicLogFactorys 
capable of generating events. Therefore an implementation needs to choose a different 
technique to announce that a log is approaching full. Some example techniques are for 
the BasicLog to write to stderr or syslog. 

Specification IDL 
No change 

Actions taken: 
Completed.
Actions taken:
June 1, 1999: received issue
July 27, 1999: closed issue
Discussion: 

End of Annotations:=====
Date: Tue, 1 Jun 1999 13:13:27 -0400 (EDT)
Message-Id: <199906011713.NAA20100@emerald.omg.org>
From: spruce@fc.hp.com
To: juergen@omg.org, web-incoming@omg.org
Subject: Issue Report
Content-Type: text
X-UIDL: 336bdec83a027e7b8ccca93285c3a36a
Status: RO

Name: Stephen Spruce
Company: Hewlett-Packard
mailFrom: spruce@fc.hp.com
Notification: Yes
Specification: Telecom Log Service
Section: 
Formal #: dtc/05-01-99
Version: 
Revision_Date: 05-24-99
Page: 
Nature: Revision
Severity: Minor
full_desc: ISSUE
-----
(from Matt Braun: mjb2@cs.wustl.edu)

Should the Log interface define the get_capacity_thresholdlist()
and set_capacity_thresholdlist() operations? The BasicLog interface
inherits from Log and yet thresholds are meaningless in the context
of the BasicLog Why are they defined in Log and not in event and
notify log? And should BasicLog even bother checking the parameters or
doing anything?

submit: Submit Issue Report