W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1999

Re: Resend: Re: IPP> Chunked POST: SUMMARY

From: <kugler@us.ibm.com>
Date: Mon, 25 Jan 1999 09:24:44 -0700
To: http-wg@hplb.hpl.hp.com
Cc: ipp@pwg.org
Message-Id: <87256704.005A2A56.00@d53mta08h.boulder.ibm.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/323

  <9901240030.aa0531-@paris.ics.uci.edu> wrote:
Original Article: http://www.egroups.com/list/http-wg/?start=8506
> >Roy, would implementing it as a Java servlet be braindead?
> That depends on the servlet API.
Unfortunately, the Servlet API spec is silent on the issues of
Content-Length and chunking.

> >Should every
> >application that uses HTTP as a transport build in its own HTTP
> >implementation, even if one is already available on the platform?
> No application should use HTTP as a transport.

I don't think everyone would agree with that statement.  See

Network Working Group                                        Keith Moore
Internet-Draft                                   University of Tennessee
5 August 1998                                           Patrik Faltstrom
Expires: 5 February 1999                                           Tele2
         On the use of HTTP as a Substrate for Other Protocols

> If it used HTTP as HTTP,
> there wouldn't be any need for a separate implementation, but it would
> still be desirable to base the service on the best capabilities of HTTP
> and not on the characteristics that might be true of some other resources
> that are accessible via HTTP.
> ....Roy
Received on Monday, 25 January 1999 08:32:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:06 UTC