Quality of Service for CCM Avatar
  1. OMG Specification

Quality of Service for CCM — Open Issues

  • Acronym: QOSCCM
  • Issues Count: 8
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

simplified api (un)intall_service_reference

  • Key: QOSCCM11-3
  • Legacy Issue Number: 17442
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    The spec defines the following methods

    Cookie
    install_service_reference(
    in string service_id, in Object objref)
    raises (CCMException);
    Object
    uninstall_service_reference(in Cookie ck)
    raises (CCMException);

    it is described that the service reference id is unique, so why do we need a cookie at all. It will simplify things for users if we do:

    void
    install_service_reference(
    in string service_id, in Object objref)
    raises (CCMException);
    Object
    uninstall_service_reference(in string service_id)
    raises (CCMException);

  • Reported: QOSCCM 1.0 — Mon, 18 Jun 2012 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

QoSPropertyRegistration used but not defined

  • Key: QOSCCM11-2
  • Legacy Issue Number: 15670
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    The specification adds QoSPropertyRegistration as part of the context definition but this interface isn't defined at all in the specification

  • Reported: QOSCCM 1.0 — Fri, 1 Oct 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Casing issue, CORBA::OCtetSeq

  • Key: QOSCCM11-1
  • Legacy Issue Number: 14920
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    In the document there are several casing problems, search for CORBA::OCtetSeq, it should be CORBA::OctetSeq

  • Reported: QOSCCM 1.0 — Mon, 4 Jan 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Examples

  • Key: QOSCCM-2
  • Legacy Issue Number: 9748
  • Status: open  
  • Source: Fraunhofer FOKUS ( Tom Ritter)
  • Summary:

    More complete examples that show the actual QoSConstraint structures, the deployment of QoSEnablers, the negotiation, and the use of the COPIs would be really helpful in understanding the spec.

  • Reported: QOSCCM 1.0b2 — Thu, 18 May 2006 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Section: 8.6 Derivation of RequestInfo

  • Key: QOSCCM-1
  • Legacy Issue Number: 9735
  • Status: open  
  • Source: Fraunhofer FOKUS ( Tom Ritter)
  • Summary:

    Derivation of RequestInfo Why isn't ContainerClientRequestInfo simply derived (with no extension) from PortableInterceptor::ClientRequestInfo? This would save a step (calling request_info()) in user code. Why isn't ContainerServerRequestInfo simply derived (with no extension) from PortableInterceptor::ServerRequestInfo? This would save a step (calling request_info()) in user code.

  • Reported: QOSCCM 1.0b2 — Thu, 18 May 2006 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

ExtensionComponent and ccm_remove

  • Key: QOSCCM-5
  • Legacy Issue Number: 16253
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    Can anyone explain why the ExtensionComponent only delivers the
    ccm_remove method and not all the other methods which the
    SessionComponent has?

  • Reported: QOSCCM 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

operations in the interface StubContainerInterceptor

  • Key: QOSCCM-4
  • Legacy Issue Number: 11322
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Dr. Ansgar Radermacher)
  • Summary:

    The operations in the interface StubContainerInterceptor have an out boolean parameter called "con". It corresponds (I think) to the parameter "proceed_call" described in the text and should therefore be renamed accordingly

  • Reported: QOSCCM 1.0b1 — Thu, 30 Aug 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

QoS for CCM ComponentInstallation

  • Key: QOSCCM-3
  • Legacy Issue Number: 11319
  • Status: open  
  • Source: THALES ( Olivier Hachet)
  • Summary:

    In section 8.11.4 (deployment), the ComponentInstallation interface is
    referenced. It no more part of the current CCM specification and shall be
    replaced by elements of D&C spec. NodeManager for the physical
    transportation and NodeApplicationManager for the loading of libraries

  • Reported: QOSCCM 1.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT