Version 1.1.1.1 of ais/ai-00069.txt

Unformatted version of ais/ai-00069.txt version 1.1.1.1
Other versions for file ais/ai-00069.txt

!standard D.4 (15)          95-11-01 AI95-00069/01
!class confirmation 95-07-27
!status WG9 approved 95-06-14
!status ARG approved (subject to editorial review) 10-0-0 95-11-01
!status received 95-07-27
!subject One queuing policy per partition.
!summary 95-07-27
An implementation need not support more than one queuing policy per partition. For example, the implementation need not support both FIFO_Queuing and Priority_Queuing in the same partition.
!question 95-07-27
D.4(15) says:
Implementation Permissions
15 Implementations are allowed to define other queuing policies, but need not support more than one such policy per partition.
Does the permission to support only one policy per partition apply only to the "other" (implementation defined) policies? (No.)
!response 95-07-27
The second part of the Implementation Permission applies to all queuing policies.
10.1.5(9) says:
9 An implementation may place restrictions on configuration pragmas, so long as it allows them when the environment contains no library_items other than those of the predefined environment.
This implies that an implementation need not support more than one queuing policy per partition, whether or not the policy is implementation defined. Of course, the "other" policies mentioned in D.4(15) are implementation defined, so the implementation can restrict them in any way it sees fit. Required support for more than one policy in the same partition would be an implementation burden that is not worthwhile.
!appendix

!section D.4(15)
!subject Support for more than one queuing policy?
!reference RM95-D.4(15)
!from Bob Duff
!reference as: 95-5214.d Robert A Duff 95-7-8>>
!discussion

I'm submitting this on behalf of Robert Dewar.

D.4(15) says:

			  Implementation Permissions

 15   Implementations are allowed to define other queuing policies, but need
 not support more than one such policy per partition.

Does the permission to support only one policy per partition apply only
to the "other" (implementation defined) policies?  I think the intent is
that it should apply to all policies.  For example, the implementation
need not support both FIFO_Queuing and Priority_Queuing in the same
partition.  It would be silly to grant the permission only for
implementation defined policies -- since they are implementation
defined, the implementation can presumably restrict them however it sees
fit.



****************************************************************

Questions? Ask the ACAA Technical Agent