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

Re: IPP>MOD - HTML and IPP streams

Robert Herriot (Robert.Herriot@Eng.Sun.COM)
Thu, 27 Feb 1997 13:06:37 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Tom Hastings: "IPP> REQ - unable to read issues.pdf and closed.pdf with 2.1"
Previous message: Robert Herriot: "Re: IPP>MOD - Updated Diagram"
Maybe in reply to: rdebry@us.ibm.com: "IPP>MOD - HTML and IPP streams"
Next in thread: Carl-Uno Manros: "IPP> MOD - Re. HTML and IPP streams"
Next in thread: Randy Turner: "Re: IPP>MOD - HTML and IPP streams"

> 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.

Next message: Tom Hastings: "IPP> REQ - unable to read issues.pdf and closed.pdf with 2.1"
Previous message: Robert Herriot: "Re: IPP>MOD - Updated Diagram"
Maybe in reply to: rdebry@us.ibm.com: "IPP>MOD - HTML and IPP streams"
Next in thread: Carl-Uno Manros: "IPP> MOD - Re. HTML and IPP streams"
Next in thread: Randy Turner: "Re: IPP>MOD - HTML and IPP streams"