IPP Mail Archive: Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?
Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?
papowell@astart.com
Mon, 8 Sep 1997 21:27:23 -0700 (PDT)
> From ipp-owner@pwg.org Fri Sep 5 17:37:43 1997
> Date: Fri, 5 Sep 1997 16:59:31 -0700
> From: Robert.Herriot@Eng.Sun.COM (Robert Herriot)
> To: Robert.Herriot@Eng.Sun.COM, jkm@underscore.com
> Subject: Re: IPP>MOD Why use Job-Id instead of Job-URI for Jobs?
> Cc: ipp@pwg.org
>
>
> > From jkm@underscore.com Fri Sep 5 16:21:30 1997
> >
> > Robert Herriot wrote:
> > >
> >
> >
> > > Even if we did specify the syntax for a Job-URI, there is still the
> > > problem that its printer-URI constituent might be different from
> > > the printer-URI to which the job was submitted. That is also a
> > > problem for a gateway because a gateway assumes that a job is named by
> > > the printer to which the job was submitted plus a job-Id. If the
> > > job-printer is different, the gateway would have to "remember" that.
> >
> > I believe this is a different issue that should not be confused with
> > the issue of standard URI syntax definitions.
> >
>
> I disagree. A parseable Job-URI would still be a problem for gateways.
> That is, they would still need a job submitted to Printer P to have
> a job identification of (P,n) where n is some integer.
> >
>
Actually, there would need (P,s) where s is a STRING or even a set of tokens.
Most implementations assume that s is either the user name or a job 'number'
but that is purely a matter of implementation.
Patrick Powell