wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: multiple sutiation categories in an event
- From: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
- To: <wsdm@lists.oasis-open.org>
- Date: Wed, 17 Nov 2004 16:39:26 -0500
It may be interesting to hear opinions of the TC
members about what William has proposed as a way to move forward with the
situation categories: allow multiple situation categories in an
event.
-- Igor
Sedukhin
..
(igor.sedukhin@ca.com)
-- (631)
342-4325
..
1 CA Plaza, Islandia, NY 11749
Ok, if we accept what you propose I may let this
go. It is not getting any better, it seems...
I
suggest that we decice this on the call tomorrow.
-- Igor
Sedukhin
..
(igor.sedukhin@ca.com)
-- (631)
342-4325
..
1 CA Plaza, Islandia, NY 11749
Igor,
Do you think that allowing more than one situation category
would cover your examples better? If events are related to more than one it
can be expressed in the message...
William
#1 there is a
property which is mydevice:ConnectedTo which indicates the name of the network
which the device is currently connected to e.g. Nothing, GSM900, GSM1900, GSM
1800, 802.11g, 802.11.b etc. Such property is writeable and could be set by the
manager, so this is configuration. When a property change event has to be
generated by an manageability implementation for this device, what would be the
situation category to put in the event data: Configuration, Connection
or Report? What part of the WSDM spec will be sufficient to describe the
choice for an average developer?
#2 there is an
OperationalState property and an event is generated for this property change
when state transition from DOWN:CRASHED to DOWN:STOPPED. What does one put as a
situation category: Availability, Stop or Report? In this case,
availability did not change so it is just a report, but the operational state
certainly defines the availability. DOWN:STOPPED is a state which indicates that
resource is stopped, but its availability didn't really change in case of this
transition. However this would not be true if transitioning from UP to
DOWN:STOPPED, in that case the availability changes. A) What in the spec
would lead one to be crystal clear on which situation category to pick in this
case? B) What if the event generator has no knowwledge of the actual resource
state model? How would it decide between UP->DOWN:STOPPED and
DOWN:CRASHED->DOWN:STOPPED?
-- Igor
Sedukhin
..
(igor.sedukhin@ca.com)
-- (631)
342-4325
..
1 CA Plaza, Islandia, NY 11749
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]