T.R | Title | User | Personal Name | Date | Lines |
---|
1262.1 | For RSM, see NOTED::RSM | TOOK::MINTZ | Erik Mintz | Thu Jul 18 1991 08:36 | 1 |
| I don't know aobout DECros, but RSM has a notes conference NOTED::RSM.
|
1262.2 | DECros Notes Conference... | TENERE::SILVA | Carl Silva - Telecom Eng - DTN 828-5339 | Thu Jul 18 1991 10:43 | 4 |
|
TAEC::DEC_ROS for the DECros product.
carl
|
1262.3 | commonality | TOOK::MATTHEWS | | Fri Jul 19 1991 15:45 | 9 |
| DECros is planned to provide CMIP for customers who want to write
their own network management applications. DECmcc on the other hand
layers an access module on top of a protocol implementation so that
customers do not have to write their own management applications.
Both contain implementations of CMIP. Some future DECmcc components
may used DECros as a component.
wally
|
1262.4 | Thanks for pointers and discussion | IJSAPL::WOODROW | From E101 to VAX and beyond... | Sun Jul 21 1991 12:38 | 3 |
| Thanks very much for the pointers and discussion.
Peter
|
1262.5 | ROS is not the hard part | NAC::ENGLAND | | Mon Jul 22 1991 18:48 | 9 |
| I tried implementing CMIP as a ROS application once, and found that
there was remarkably little benefit in this approach. Why? Because
the heart and soul of CMIP are the entity (managed object) instance,
and the attribute/argument list. None of these things can be described
to ROS, because in an extensible director (or agent) we don't know
what attributes exist until runtime.
ben
|