IPP Mail Archive: Re: IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE MODEL DOCUMENT

Re: IPP> MOD - UPDATE FOR STATUS CODE KEYWORDS IN THE MODEL DOCUMENT

Robert Herriot (Robert.Herriot@Eng.Sun.COM)
Wed, 21 May 1997 13:48:43 -0700

Good job. I have some comments below

Bob Herriot

> From carterk@us.ibm.com Wed May 21 12:48:36 1997
>
Is this really necessary, especially if the returned attributes indicate
which are unsupported. This is a case of half-full versus half-empty.

> 4.4.2.2 successful-attribute-ignored (IPP)


I'm not sure if this is a useful error, or even likely to happen.

>
> 4.4.4.5 server-error-printer-error (IPP)
>
> A printer error, such as a paper jam, occurs while the IPP Printer
> processes a Print-Job or Send-Data operation. The response shall contain
> the Job Status with the specific error and should contain a Message
> describing the error. An IPP application should check the Job Status
> in the response for the specific error.

I would expect the client to block on a write and that it wouldn't
clear until the server got enough space to write the data.

>
> 4.4.4.6 server-error-write-fault (IPP)
>
> A write error, such as a memory overflow (i.e. the document data
> exceeds the memory of the Printer) or a disk full condition, occurs
> while the IPP Printer processes a Print-Job or Send-Data operation.

With the changes from last week where all Printers support PrintJob
(1 document per job) and some support CreateJob/SendJobData (1 or
more documents per job), this message isn't needed. The error
server-error-operation-not-implemented handles this problem instead.

>
> 4.4.4.7 server-error-too-many-documents-in-job (IPP)
>