| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 945.1 | clarification on "object classes" | TOOK::CALLANDER | | Tue Apr 23 1991 21:09 | 9 |
| I am uncertain what in DECmcc terms you are referring to by "object classes".
If you could clarify that would be helpful.
If you mean how many different entity classes can be merged into the system
and managed through DECmcc the limit it theoretically infinite. The same
is true about specific instances (such as the instance goste, my workstation,
of the entity class NODE4). DECmcc doesn't place limits outside of those
that the users environment dictates; you can only register as many nodes
as you own and as many as you have enough memory to store information on.
|
| 945.2 | "entity class" was meant | NANTES::DUMOULIN | | Wed Apr 24 1991 08:03 | 14 |
| Thanks for your answer.
I agree with you, the customer question is about entity classes.
I looked into DNS and found out an attribute called MCC_CLASS which
seems to be coded on four bytes (value of 08 00 00 00), in a node4
entity.
- Is this attibute related to the entity class ?
- If yes, is the four bytes coding the actual limit for the number
of entity classes ?
|
| 945.3 | The number of potential entity classes is infinite | TOOK::MATTHEWS | | Thu May 02 1991 13:54 | 16 |
| What you see in DNS is a temporary implementation mechanism. It was
chosen to be arbitrarily large. It is not tightly linked with entity
class at all. The number of supported entity classes is theoretically
unlimited. The actual entity class code encoding allows it to be
infinitely extended. When putting it into DNS we used the attribute
MCC_CLASS as a DNS specific implementation. It can be easily extended
in the future, so this should not be referenced as a limitation.
The practical limit is how big is the dictionary which contains
the entity model of all the entity classes that a customer will want
to use. For example, the registry may be able to issue new entity
class codes but the customers dictionary may be so large that
he can't practically add a new entity class without buying more
storage or assigning a different size to his virtual storage, etc.
wally
|
| 945.4 | We'll be able to define new classes for "awhile" | CAPN::SYLOR | Architect = Buzzword Generator | Fri May 03 1991 01:12 | 5 |
| To be fair, we did architect an upper bound into EMA (V1). that bound
is 2^(280). I think that number is large enough so that every atom in
the galaxy could have its own class :-) This is not a problem :-)
Mark
|