I think this is a good example of the things that we need to put in an
Implementor's Guide document. Formally, as we are referencing IETF's
HTTP 1.1, all IPP implementations MUST support "chunking". However, I
think it would be smart for an actual implementation to also support
using HTTP 1.0 to allow for maximum interoperability. E.g. in Xerox we
have had to base our current client code (written in Java) on HTTP 1.0,
as the JavaSoft libraries do not yet support some of the HTTP 1.1
features. These problems will disappear over time, but we also need to
get things working short term.
> -----Original Message-----
> From: Carl Kugler [mailto:kugler at us.ibm.com]
> Sent: Friday, July 24, 1998 9:52 AM
> To: ipp at pwg.org> Subject: IPP> Implementation question re.: chunking
>>> draft-ietf-ipp-protocol-06.txt says the client and server
> MUST support the "chunked" transfer encoding when receiving.
> My question is: Can we count on this? I.e., if our client
> always transmits requests using the "chunked" transfer
> encoding, will we be able to interoperate with the vast
> majority of IPP server implementations?