W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997

Re: indefinite server-push (was 'Last-Modified in chunked footer')

From: Ben Laurie <ben@algroup.co.uk>
Date: Mon, 15 Sep 1997 19:38:50 +0100
Message-Id: <341D80BA.D5887456@algroup.co.uk>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4410
Larry Masinter wrote:
> In reply to:
> > I think that "indefinitely long server push" should be explicitly
> > disallowed. What's a robot to do, for example? I suppose this
> > is a different topic.
> Ben Laurie said:
> > Try ringing you local TV station and telling them they have to stop
> > broadcasting after 3 hours, because your VCR runs out of tape. :-)
> but seriously, shouldn't there be an expectation that a single
> HTTP request should get a complete reply, properly terminated,
> within a relatively small amount of time, and that a continuous
> entity body without termination (delivered through chunked encoding,
> perhaps) is not a valid HTTP response?

If there should be such an expectation, we should have said so long ago.
Servers commonly push effectively unlimited amounts of data already, and
I'd guess that this will become more common as time goes by.

> If we don't disallow such things, a proxy implementation which attempted
> to buffer complete responses before sending them on would be
> non-compliant.

A proxy which attempts to buffer complete responses is broken, so it may
as well be non-compliant.



Ben Laurie            |Phone: +44 (181) 994 6435|Apache Group member
Freelance Consultant  |Fax:   +44 (181) 994 6472|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |Apache-SSL author
A.L. Digital Ltd,     |http://www.algroup.co.uk/Apache-SSL
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache
Received on Monday, 15 September 1997 11:43:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC