Re: Fast HTTP - a hyper-text transfer protocol for tommorows networks.

miked@CERF.NET (Michael A. Dolan)

Mail folder: WWW Talk Apr 94-present
Next message: Niels P. Mayer: "http://www.eit.com/software/winterp/winterp.html (WINTERP home page)"
Previous message: Matt Womer: "Mosaic mail reading..."
Maybe in reply to: Paul "S." Wain: "Re: Fast HTTP - a hyper-text transfer protocol for tommorows networks."

Errors-To: listmaster@www0.cern.ch
Date: Thu, 30 Jun 1994 21:23:51 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406301623.JAA07111@nic.cerf.net>
Errors-To: listmaster@www0.cern.ch
Reply-To: miked@CERF.NET
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: miked@CERF.NET (Michael A. Dolan)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Fast HTTP - a hyper-text transfer protocol for tommorows networks.
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Mailer: <Windows Eudora Version 2.0.2>
X-Mailer: <Windows Eudora Version 2.0.2>
Content-Type: text/plain; charset="us-ascii"
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Mime-Version: 1.0

At 10:10 PM 6/29/94 +0200, Simon E Spero wrote:
>Fast HTTP
>---------

I see this would reduce the httpd header parsing somewhat and allow for
batched object requests, but:

1. How does the client receive unsolicited and/or solicited, but delayed
objects ?  Does the client have an fhttpd object server as well, or do
you keep the command TCP connection alive for all transactions (ala FTP) ?

2. Which end "looks-ahead" ?  Does the fhttpd scan the requested objects
for possibilities or does the client batch up requests ?

        Mike
------------------------------------
Michael A. Dolan - miked@cerfnet.com 
TerraByte Technology (619) 445-9070