Mobile Management Tree Very Complex - Githubissues

osgi / bugzilla-archive

Archive of OSGi Alliance Specification Bugzilla bugs. The Specification Bugzilla system was decommissioned with the move to GitHub. The issues in this repository are imported from the Specification Bugzilla system for archival purposes.

0 stars 1 forks source link

Mobile Management Tree Very Complex #15

Closed bjhargrave closed 18 years ago

bjhargrave commented 18 years ago

Original bug ID: BZ#16 From: @bjhargrave Reported version: R4

bjhargrave commented 18 years ago

Comment author: @bjhargrave

Tue, May 24 2005 05:31:32 Request created by pkriens

The MMT for Log and Configuration Admin are overly complicated. The Log introduces a complete new spec which is protocol based (TNDS) which would not be necessary if we remained in the Dmt spec, which I think is feasible.

The Configuration Admin tries to be compatible with the configuration admin. I think it is better to make a simple tree in DMT and map that to configuration admin. Even with this overly complex tree we cannot guarantee full compatibility. Lets keep it simple, backward compatibility is hardly an issue for MEG.

bjhargrave commented 18 years ago

Comment author: @bjhargrave

Tue, May 24 2005 05:40:37 Comments added by pkriens

Additional issues with the alert

The TNDS format seems binary, this may increase the payload
The Alert interface only allows strings to be passed, meaning that the whole log file must be placed in a string before it is shipped. This will take a lot of memory.

bjhargrave commented 18 years ago

Comment author: @bjhargrave

Thu, Jun 2 2005 13:34:50 Comments added by pkriens

Cleanup of the Log tree has happened, it does not use alerts anymore.

We discussed the cleanup of the data type handling of Configuration Admin and Monitoring. This looks feasible if we restrict the data types of CM in the MEG document. We can then map directly DMT Data items to the configuration dictionary. Any data to the configuration dictionary must be visible in the tree, albeit in another data type. I.e. a short is converted to a long. We have to look at the implications on autoconf.xml

This looks very promising but people are too busy now to look further. We postpone the further discussion to next week and see if one of us has time to make a proposal.

bjhargrave commented 18 years ago

Comment author: @bjhargrave

Thu, Jun 23 2005 07:07:28 Comments added by gabor.pecsy@ nokia.com

Peter still tries to make a proposal next week. The issue is to be closed at that time.