IPP> Identifying jobs in requests

IPP> Identifying jobs in requests

IPP> Identifying jobs in requests

Randy Turner rturner at sharplabs.com
Wed Jul 16 22:18:32 EDT 1997


Paul Moore wrote:


> The transport layer part of the client side needs to know the URL. The
>
> application layer part needs to know the job IDs. These two layers
> should be kept separate.
>
> > -----Original Message-----
> > From: Larry Masinter [SMTP:masinter at parc.xerox.com]
> > Sent: Wednesday, July 16, 1997 5:30 PM
> > To:   Paul Moore
> > Cc:   'ipp at pwg.org'
> > Subject:      Re: IPP> Identifying jobs in requests
> >
> > > This has the advantage that the client only needs to know one URL
> > for
> > > all operations on a given printer.
> >
> > Why is it an advantage to have to know the Job ID instead of
> > the Job URL? What is the nature of the advantage?




It would seem to be more sound for Job-IDs to be included, if URLs were
basically
out of band to the fundamental IPP model; but the last time I checked,
the model document
considers URLs to be the primary identifiers for IPP objects (or has
this changed radically also?)


Randy



More information about the Ipp mailing list