IPP Mail Archive: Re: IPP> New IPP Model Document

IPP Mail Archive: Re: IPP> New IPP Model Document

Re: IPP> New IPP Model Document

Scott Isaacson (SISAACSON@novell.com)
Fri, 29 May 1998 16:19:56 -0600

As I recall,=20
the only reason that the printer-uri/job-uri attributes are in
protocol at the IPP layer, is because we wanted to be
consistent with possibly future mappings of IPP onto=20
protocols other than HTTP where we didn't have
equivalent routing info. These attributes in the IPP
payload are totally redundant and they are not needed
in the HTTP mapping.

Maybe it was a bad idea to add them, since many
server implementations behind a generic web server
(as Randy points out) will work fine even if it never
even validates the values of these attributes that are
internal to the application/ipp blob.

Scott

>>> Jay Martin <jkm@underscore.com> 05/29 3:51 PM >>>
> snip...
>On the other hand, if the HTTP request header takes precedent,
>then why are we specifying printer-uri/job-uri at all at the
>IPP protocol level? Aren't we asking for trouble when the
>HTTP request header and the corresponding IPP attributes don't
>match (with regard to interoperability)?

...jay

----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------

Turner, Randy wrote:
>=20
> This may be a difficult requirement to meet if an IPP implementation is
> built as an extension to a generic web server (like Apache).
>=20
> Randy
>=20
> -----Original Message-----
> From: Jay Martin [SMTP:jkm@underscore.com]=20
> Sent: Friday, May 29, 1998 2:34 PM
> To: ipp@pwg.org=20
> Cc: Puru Bish
> Subject: Re: IPP> New IPP Model Document
>=20
> After thinking about this, I tend to agree with Puru's
> statement:
>=20
> >From "Tom Hastings"
> >
> > :: In fact, the HTTP request header URI, if persent, takes
> precedence"
> > (over printer-uri/job-uri operation attributes).
> >
> > I think it should be the other way around. I feel the
> > printer-uri/job-uri, supplied by IPP client, should have
> higher
> > precedence to an IPP server than the HTTP header URI.
>=20
> ...jay
>=20
>=20
> ----------------------------------------------------------------------
> -- JK Martin | Email: jkm@underscore.com=20
> --
> -- Underscore, Inc. | Voice: (603) 889-7000
> --
> -- 41C Sagamore Park Road | Fax: (603) 889-2699
> --
> -- Hudson, NH 03051-4915 | Web:
> http://www.underscore.com --
>=20
> ----------------------------------------------------------------------