> From rdebry at us.ibm.com Fri Jul 18 14:33:31 1997
>> > From rdebry at us.ibm.com Fri Jul 18 08:58:03 1997
> >
> >
> > 1) When the job is rejected, shouldn't the error code say something
> > like 'client-error-attribute-value-unsupported'? Otherwise it is not
> > clear that the attribute itself is supported, but the supplied value is not.
>> We have one status-code for both 'attribute not supported' and 'attribute value
> not supported' because a job could be rejected because both problems exist.
> The collection of unsupported attributes returned specify that it is
> the attribute that is unsupported by returning the attribute in the
_________________________________
> response with a value of "unsupported".
______________
>> <RKD> So how do you know it is the value that is unsupported?
Perhaps, I wasn't sufficiently clear. The 'unsupported attributes'
output parameter contains a list of rejected attributes. The printer
takes attributes with unsupported values and puts them into the
response with no change. The printer takes attributes that are not
supported and puts them into the response with their value set to
"unsupported" which in the protocol is an "out-of-band" value that
works for any type. A printer may put all such attributes in the
response, or only some of them. In other words, a Printer can
accumulate all unsupported attributes before it rejects the job or it
can reject the job immediately after it finds the first bad attribute.
>>