IPP>MOD Why use Job-Id instead of Job-URI for Jobs?

IPP>MOD Why use Job-Id instead of Job-URI for Jobs?

IPP>MOD Why use Job-Id instead of Job-URI for Jobs?

Robert Herriot Robert.Herriot at Eng.Sun.COM
Wed Sep 10 14:07:08 EDT 1997


> From hastings at cp10.es.xerox.com Tue Sep  9 19:01:45 1997
> 
> At 14:10 09/09/97 PDT, Robert Herriot wrote:
> >
> >
> >The gateway cannot use some extended attribute to store the LPD Job-Id in
> >because an IPP server would discard attributes it doesn't support.
> 
> Well, we certainly could add a "job-client-id" attribute to IPP, so that
> gateways would have a place to store an opaque "handle" in an IPP job.
> That seems a simple solution to help gateways and is something we
> have in DPA as the "job-client-id" and the Job MIB as the jobSubmissionID
> table which is a map from the client's id to the server's jmJobIndex.
> 


I have specifically avoided suggesting that we add a job-client-id job
attribute because it would have to be mandatory in order to offer a
solution to an LPD-to-IPP gateway. I don't think it is reasonable for
all implementations to support such an attribute, and I don't want to
support it for an IPP-to-LPD gateway because the gateway would then
have to maintain state for a client that sends it to the IPP-to-LPD
gateway.



More information about the Ipp mailing list