Return to CIM_MarkerService.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_MarkerService.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:20 2012 UTC (12 years, 5 months ago) by marek Branch: MAIN CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824 Branch point for: TASK-PEP317_pullop-branch BUG#:9155 TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS DESCRIPTION: |
// Copyright (c) 2005 DMTF. All rights reserved. // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath // qualifier values to CIM Schema.</change> // ================================================================== // CIM_MarkerService // ================================================================== [Version ( "2.6.0" ), UMLPackagePath ( "CIM::Network::QoS" ), Description ( "MarkerService represents the general process of marking a " "selected field in a network packet with a specified value. " "Packets are marked in order to control the conditioning that " "they will subsequently receive. Subclasses of MarkerService " "identify the specific fields to be marked, and introduce " "properties to represent the values used in marking these " "fields. Markers are usually invoked as a result of a preceding " "classifier match. \n" "\n" "MarkerService is a concrete class because its superclass " "(ConditioningService) is concrete. While this class can be " "instantiated, an instance of it does not accomplish anything, " "because both the field to be marked and the value used to mark " "it are defined in subclasses. \n" "\n" "MarkerService is modeled as a ConditioningService so that it " "can be aggregated into a QoSService (using the " "QoSConditioningSubService association). This association " "indicates that the MarkerService\'s functionality underlies " "the QoSService. MarkerService also participates in the " "NextService association to identify the subsequent " "ConditioningService(s) that act on packets after they have " "been marked." )] class CIM_MarkerService : CIM_ConditioningService { };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |