IPP Mail Archive: RE: RE: IPP> Identifying jobs in requests

RE: RE: IPP> Identifying jobs in requests

Robert Herriot (robert.herriot@Eng.Sun.COM)
Fri, 05 Jun 1998 20:46:10 -0700

--=====================_33814923==_.ALT
Content-Type: text/plain; charset="us-ascii"

We agreed recently that the following operation attributes would be ordered.
attributes-charset (always first for requests and responses)
attributes-natural-language (always second for requests and response)
printer-uri or job-uri (always third for requests, though we are discusses
whether it should be present)
job-id (always fourth for requests if present )

At 05:00 PM 6/5/98 , Paul Moore wrote:
> I think we are approaching group consensus on this. I propose that
>we remove "printer-uri" and "job-uri" as request Operation attributes, but
>leave them in their special position in the protocol.
>
> [Paul Moore] What 'special position'?
>

--=====================_33814923==_.ALT
Content-Type: text/html; charset="us-ascii"

We agreed recently that the following operation attributes would be ordered.
    attributes-charset (always first for requests and responses)
    attributes-natural-language (always second for requests and response)
    printer-uri or job-uri (always third for requests, though we are discusses whether it should be present)
    job-id (always fourth for requests if present )

At 05:00 PM 6/5/98 , Paul Moore wrote:
>       I think we are approaching group consensus on this.  I propose that
>we remove "printer-uri" and "job-uri" as request Operation attributes, but
>leave them in their special position in the protocol. 
>
>       [Paul Moore]  What 'special position'?
>

--=====================_33814923==_.ALT--