Issue 3120: Telecom Log Service issue (log_service-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: This issue concerns the Telecom Log Service as described in
the dtc/99-07-02 document.

I think the following statements in the spec are not compatible 
together:
 
 "Log forwarding is determined solely by forwarding state, it is not
  affected by the log's administrative state, availability state, log
  duration, scheduling, or log full action."
 
 "A log may be not be able to create any new log records because it is 
  full, locked, or disabled. If a log cannot create new log records when 
  a push operation is invoked, then the push operation should fail and a 
  SystemException should be raised."

If the log records are forwarded, then throwing system exceptions to
the supplier doesn't make sense. 

Resolution: 
Revised Text: 
Actions taken:
December 15, 1999: received issue
Discussion: 

End of Annotations:=====
Sender: benoit@mailhub4.libertysurf.fr
Message-ID: <3857C136.733B1DC@ooc.com>
Date: Wed, 15 Dec 1999 17:26:30 +0100
From: Benoit Foucher <benoit@ooc.com>
Organization: Object Oriented Concepts, Inc.
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.5 ppc)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org
CC: michi@ooc.com.au, ml@ooc.com, matthew@ooc.com
Subject: Telecom Log Service
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: i)-!!%mPe9V_#!!<)Q!!

Hello,

This issue concerns the Telecom Log Service as described in
the dtc/99-07-02 document.

I think the following statements in the spec are not compatible 
together:
 
 "Log forwarding is determined solely by forwarding state, it is not
  affected by the log's administrative state, availability state, log
  duration, scheduling, or log full action."
 
 "A log may be not be able to create any new log records because it is

  full, locked, or disabled. If a log cannot create new log records
when 
  a push operation is invoked, then the push operation should fail and
a 
  SystemException should be raised."

If the log records are forwarded, then throwing system exceptions to
the supplier doesn't make sense. 

Furthermore, a log record supplier who use the pull model to supply 
log records won't be notified that the log status doesn't allow
to create new log records. The spec says nothing about suppliers
who use the pull model to supply log records.

I feel like throwing system exceptions in the push() method isn't 
justified. A log record supplier who use either an event channel
or a notification event channel should just supply log records
using either the push or pull model and shouldn't expect any
log specific exceptions.

Cheers,
Benoit Foucher.
--
Benoit Foucher                          E-Mail: mailto:benoit@ooc.com
Object Oriented Concepts, Inc.          WWW:    http://www.ooc.com