> The concrete transport/encoding IPP protocol document is VERY depende=
nt
> on HTTP chunking.
I still don't get it. Could you please explain?
The original statement is:
> Encoding is HTTP independent except for chinking.
This sentence, to me, implies that there is some aspect of the IPP enco=
ding,
apart from HTTP, that depends on chunking. This is suprising news to m=
e.
The only chunking-related requirements I've found in the Protocol docum=
ent are:
1) the Server must support "chunked" Transfer-Encoding of Requests
2) the Client must support "chunked" Responses.
These requirements derive directly from RFC 2068: "All HTTP/1.1 applic=
ations
MUST be able to receive and decode the "chunked" transfer coding..."
Confused in Boulder,
Carl-III
ipp-owner at pwg.org on 04/14/98 05:34:03 PM
Please respond to ipp-owner at pwg.org
To: ipp at pwg.org
cc:
Subject: RE: IPP> Minutes from PWG IPP Meeting in Portland, OR - Apri
The abstract IPP described in the model document is not dependent on
HTTP chunking.
The concrete transport/encoding IPP protocol document is VERY dependent=
on HTTP chunking.
Randy
-----Original Message-----
From: Carl Kugler [SMTP:kugler at us.ibm.com]
Sent: Tuesday, April 14, 1998 4:25 PM
To: ipp at pwg.org
Subject: Re: IPP> Minutes from PWG IPP Meeting in
Portland, OR - Apri
> IPP is not transport neutral. Encoding is HTTP independent
except for
> chinking.
I assume you mean "chunking". In what way is IPP dependent on
HTTP chunking?
-Carl
=