T.R | Title | User | Personal Name | Date | Lines |
---|
1540.1 | Graphs support simple data types | TOOK::A_MOORE | | Tue Sep 24 1991 10:13 | 10 |
| The real time graph supports simple datatypes. It does not support constucted
data types.
The why is: it takes more engineering time to do more complicated datatypes.
We have to justify bells and whistles by defining user benefit or competitive
advantage. Feel free to give examples of customer benefit of this feature for
future versions.
Al Moore
|
1540.2 | Largest european SVP partner... | TENERE::HAYES | A European Telecomet ... | Wed Sep 25 1991 04:32 | 18 |
|
This was directly extracted from a requirement of my
preferred customer, which is not only a customer but
also an SVP partner, and not only an SVP partner, but
the largest european SVP partner. Guess who...
Thanks for your quick answer
Best Regards
Catherine
|
1540.3 | | TOOK::CALLANDER | MCC = My Constant Companion | Wed Sep 25 1991 19:32 | 27 |
| RE: .1
My question relates to this example :
TYPE RoutingCost = 58 RECORD
LocalCall = 1 : Unsigned8;
ExternalCall = 2 : Unsigned8;
X25Call = 3 : Unsigned8;
END ;
Let's imagine an object called Routing Path. A status
attribute (Cost) is defined as being of data type
RoutingCost.
1) - Will the generic real time graphing utility be able to
graph the LocalCall, ExternalCall and X25Call
attributes ?
Cathrine, please note that LocalCall, ExternalCall, and X25Call are
NOT attributes based upon the definition you supplied. Instead they
are portions of an attribute value. As stated by Al we will be
able to graph attribute of primitive types (numerics). I understand
the subfield idea but by doing such they have created a complex
attribute, and not the three attributes that they meant to return.
|
1540.4 | You have three attributes, not one record | BLUMON::SYLOR | Architect = Buzzword Generator | Thu Oct 24 1991 09:57 | 5 |
| This is a great example of why attributes of type record cause difficulties,
but defining each field of the record as a separate attribute would work far
better. I doubt very much that there is any reason why the 3 fields *must*
appear as one attribute, they are almost always treated as separate
values.
|