Re: IPP> Implementation question re.: chunking

Randy Turner <rturner@sharplabs.com> Fri, 24 July 1998 17:16 UTC

Delivery-Date: Fri, 24 Jul 1998 13:16:44 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA21824 for <ietf-archive@ietf.org>; Fri, 24 Jul 1998 13:16:43 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA18166 for <ietf-archive@cnri.reston.va.us>; Fri, 24 Jul 1998 13:16:33 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id NAA00987 for <ietf-archive@cnri.reston.va.us>; Fri, 24 Jul 1998 13:16:40 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Fri, 24 Jul 1998 13:12:38 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id NAA00115 for ipp-outgoing; Fri, 24 Jul 1998 13:09:12 -0400 (EDT)
Message-Id: <199807241713.KAA07045@mail.pacifier.com>
X-Sender: rturner@webmail.sharplabs.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Fri, 24 Jul 1998 10:05:26 -0700
To: Carl Kugler <kugler@us.ibm.com>
From: Randy Turner <rturner@sharplabs.com>
Subject: Re: IPP> Implementation question re.: chunking
Cc: ipp@pwg.org
In-Reply-To: <19980724165143.21038.qmail@m2.findmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipp@pwg.org

At 04:51 PM 7/24/98 +0000, you wrote:
>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?
>
>    -Carl


There are no vast majority of IPP server implementations (yet). I think the
only worry is if someone plans to deploy IPP behind a generic web server
that doesn't support chunking. However, Apache and most other of the more
popular HTTP/1.1 servers will support this. It should definitely be a
bullet item (checkoff item) at the upcoming bake-off, however.

Randy

>