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

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• 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: Simon E Spero: "Fast HTTP - a hyper-text transfer protocol for tommorows networks."

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

• 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: Simon E Spero: "Fast HTTP - a hyper-text transfer protocol for tommorows networks."