IPP Mail Archive: Re: IPP>MOD - HTML and IPP streams

Re: IPP>MOD - HTML and IPP streams

Steve Zilles (szilles@Adobe.COM)
Thu, 27 Feb 1997 14:17:26 PST

> Date: Thu, 27 Feb 1997 13:06:37 -0800
> From: Robert.Herriot@Eng.Sun.COM (Robert Herriot)
>
> > From rdebry@us.ibm.com Thu Feb 27 09:40:59 1997
> > From: rdebry@us.ibm.com
> >
> > ... I'd suggest the following relative to the use of HTML
> > and IPP:
> >
> > A Web Browser must support HTML (pretty obvious)
> >
> > An IPP Client must support IPP, and may optionally support HTML
> >
> > An IPP Server must support IPP and may optionally support HTML.
> >
> > I don't think that we can say that an IPP Server MUST support HTML in
> > order to be IPP compliant. Actually sounds pretty silly to me to say that
> > HTML is required to be IPP compliant! I don't think that this is an
> > interoperability issue, is it?
> >
>
> Actually, we did say that an IPP server must support IPP AND HTML because
> if HTML is optional, then a client which expects HTML, must have a fallback.
> If clients must have a fallback to IPP, then no server need have HTML.
>
> I think the primary issue is whether a server gives exactly the same
> information and capabilities via IPP and HTML.

I would express Rogers list of statements somewhat differently and I
think the difference is important as to why we said we would require
HTML from the user.

A Web Browser must support HTML (pretty obvious)

A Client of the IPP Model may support access to that model using an
HTML binding to the model information.

A Client of the IPP Model may support access to that model using an IPP
defined binding to the model information (see Protocol Group)

An IPP Server must support must support both the IPP defined binding and
the HTML binding to the model information

This recognizes the difference between supporting the model and
supporting a partiucular binding to the model. At least from my point of
view, this is why we made the statement.

After some thought, I would be happy if a server only had to implement
the HTML binding, both for query and submission.
Steve