-Carl
owner-ipp@pwg.org on 05/29/98 05:03:59 PM
Please respond to owner-ipp@pwg.org
To: Carl Kugler/Boulder/IBM@ibmus
cc: ipp@pwg.org
Subject: Re: IPP> MOD - new model document with fixes for typos and m
A simpler clarification fix would be to delete the word "processed"
in "received, validated, processed, ..."
so that it would read:
In the case of a Print-Job operation, the
'successful-ok' status code indicates that the request was successfully=
received, and validated, and that the Job object has been created; it
does not indicate that the job has been printed.
Tom
At 13:28 05/29/1998 PDT, Carl Kugler wrote:
>I question this new definition:
>"13.1.2.1 successful-ok (0x0000)
>"The request has succeeded. In the case of a Print-Job operation, the=
>'successful-ok' status code indicates that the request was successfull=
y
>received, validated, processed, and that the Job object has been creat=
ed; it
>does not indicate that the job has been printed. The transition of th=
e Job
>object into the 'completed' state is the only indicator that the job h=
as been
>printed.
>
>given the definition of 'processing' in section 3.1.7:
>"Job submission time is the point in time when a client issues a creat=
e
>request. The initial state of every Job object is the 'pending' or
>'pending-held' state. Later, the Printer object begins processing the=
print
>job. At this point in time, the Job object's state moves to 'processi=
ng'.
>This is known as job processing time. There are validation checks tha=
t
must be
>done at job submission time and others that must be performed at job
processing
>time.
>
>I don't believe that successful-ok (0x0000) really indicates that the =
request
>was successfully "processed". Or at least there is the danger of conf=
usion
>here between "request processing" and "job processing". Perhaps "requ=
est
>processing" needs a definition.
> -Carl
>
>
=