Issue 10534: Type Mode is not clearly defined                                                                                                                                                                        (rtc-ftf)
Source: Hitachi (Dr. Saku Egawa, saku.egawa.qm@hitachi.com)
Nature: Uncategorized Issue
Severity: 
Summary: Type Mode is not clearly defined in the current specification.

    *

      Mode is used but not defined in PIM.
    *

      In the IDL, Mode is defined as an interface but it seems better to be an enumeration.
    *

      ModeList is defined but never used.
    *

      Since supported modes may vary between components, using a common Mode type in all components may not be useful. 

Proposed Resolution

    *

      Define Mode as an integer in PIM and PSM/IDL, and let the component developer assign arbitrary numbers to modes of the component.
    *

      Delete ModeList from the IDL. 

Discussion

I myself think using integer as Mode is not so good manner. -- Saku Egawa
Resolution: It is not correct that Mode is not defined in the PIM. It is defined in section 7.3.3.5. It is a class with no attributes or operations. Even though there are not currently any operations, a mode is semantically an object, and so the type should remain a class. An enumeration is not appropriate, because there are no well-known instances that are common to all mode-capable components; each component implementation defines its own.
ModeList should be removed from the IDL. It is left over from a previous draft of the specification and is obsolete.

Revised Text: Remove the declaration "typedef sequence<Mode> ModeList;" from Annex A and from RTC.idl.
Actions taken:
December 21, 2006: received issue
January 15, 2008: closed issue
Discussion: 

End of Annotations:=====
MG issue 10534: Type Mode is not clearly defined

Source: Hitachi (Saku Egawa, saku.egawa.qm@hitachi.com)

Severity: Minor

Disposition: Resolution Proposed

Summary

Type Mode is not clearly defined in the current specification.

    *

      Mode is used but not defined in PIM.
    *

      In the IDL, Mode is defined as an interface but it seems better to be an enumeration.
    *

      ModeList is defined but never used.
    *

      Since supported modes may vary between components, using a common Mode type in all components may not be useful. 

Proposed Resolution

    *

      Define Mode as an integer in PIM and PSM/IDL, and let the component developer assign arbitrary numbers to modes of the component.
    *

      Delete ModeList from the IDL. 

Discussion

I myself think using integer as Mode is not so good manner. -- Saku Egawa

Resolution

Revised Text