Sophie

Sophie

distrib > Fedora > 13 > x86_64 > by-pkgid > e01f19d41597cbaefda70b1cbd9cf6b0 > files > 887

cim-schema-docs-2.22.0-2.fc12.noarch.rpm

<head><META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="mof.css" xmlns:lxslt="http://xml.apache.org/xslt">
<title>DMTF Schema Documentation Schema Documentation</title>
</head><html>
<body bgcolor="White">
<hr> 
</hr>
<a name="CIM_NextScheduler"></a>
<H1>Class CIM_NextScheduler<BR>extends <a href="CIM_NextService.html">CIM_NextService</a>
</H1>This association is a subclass of NextService, and defines a predecessor-successor relationship between Packet SchedulingServices. In a hierarchical queuing configuration (where a second scheduler treats the output of a first scheduler as a single, aggregated input), the two schedulers are related via the NextScheduler association.<h3>
					Table of Contents<br>
<a href="#c_hierarchy">Hierarchy</a>
<br>
<a href="#c_subclasses">Direct Known Subclasses</a>
<br>
<a href="#c_qualifiers">Class Qualifiers</a>
<br>
<a href="#c_properties">Class Properties</a>
<br>
<a href="#c_methods">Class Methods</a>
<br>
</h3>
<hr> 
</hr>
<H2>
<a name="c_hierarchy">Class Hierarchy</a>
</H2>
<a href="CIM_NextService.html">CIM_NextService</a>
<br data="@NAME"> &nbsp;   &nbsp;|<br> &nbsp;  &nbsp;+--<b>CIM_NextScheduler</b>
<br data="CIM_NextScheduler -- CIM_NextService">
<H2>
<a name="c_subclasses">Direct Known Subclasses</a>
</H2>
<a href="CIM_FailNextScheduler.html">CIM_FailNextScheduler</a>
<BR>
<H2>
<a name="c_qualifiers">Class Qualifiers</a>
</H2>
<TABLE BORDER="1" CELLPADDING="1" WIDTH="100%">
<TR>
<TH>Name</TH><TH>Data Type</TH><TH>Value</TH>
</TR>
<TR>
<TD VALIGN="TOP">Association</TD><TD VALIGN="TOP">boolean</TD><TD VALIGN="TOP">true</TD>
</TR>
<TR>
<TD VALIGN="TOP">Description</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">This association is a subclass of NextService, and defines a predecessor-successor relationship between Packet SchedulingServices. In a hierarchical queuing configuration (where a second scheduler treats the output of a first scheduler as a single, aggregated input), the two schedulers are related via the NextScheduler association.</TD>
</TR>
<TR>
<TD VALIGN="TOP">UMLPackagePath</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">CIM::Network::QoS</TD>
</TR>
<TR>
<TD VALIGN="TOP">Version</TD><TD VALIGN="TOP">string</TD><TD VALIGN="TOP">2.7.0</TD>
</TR>
</TABLE>
<H2>
<a name="c_properties">Class Properties</a>
</H2>
<H3>Association References</H3>
<TABLE BORDER="1" CELLPADDING="1" WIDTH="60%">
<TR>
<TH>Name</TH><TH>Class Origin</TH><TH>Reference Class</TH>
</TR>
<TR>
<TH VALIGN="TOP">FollowingService</TH><TD VALIGN="TOP">CIM_NextScheduler</TD><TD VALIGN="TOP"><a href="CIM_PacketSchedulingService.html">CIM_PacketSchedulingService</a></TD>
</TR>
<TR>
<TH VALIGN="TOP">PrecedingService</TH><TD VALIGN="TOP">CIM_NextScheduler</TD><TD VALIGN="TOP"><a href="CIM_PacketSchedulingService.html">CIM_PacketSchedulingService</a></TD>
</TR>
</TABLE>
<h2>
<a name="c_methods">Class Methods</a>
</h2>
</body>
</html>