Quality of Service for CCM Avatar
  1. OMG Specification

Quality of Service for CCM — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
QOSCCM-2 Examples QOSCCM 1.0b2 open
QOSCCM-1 Section: 8.6 Derivation of RequestInfo QOSCCM 1.0b2 open

Issues Descriptions

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