Re: Extension to HTTP V1.x (was HTTP RFC)

ellson@hotsand.att.com (John Ellson)

Mail folder: WWW Talk Apr 94-present
Next message: burchard@geom.umn.edu: "Re: Statelessness"
Previous message: Christopher McRae: "Re: Extension to HTTP V1.x (was HTTP RFC) "
Maybe in reply to: Jared Rhine: "Re: Extension to HTTP V1.x (was HTTP RFC)"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 17 May 1994 05:25:24 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9405170321.AA00617@hotsand.dacsand>
Errors-To: listmaster@www0.cern.ch
Reply-To: ellson@hotsand.att.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: ellson@hotsand.att.com (John Ellson)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Extension to HTTP V1.x (was HTTP RFC)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

> From: mcrae@ora.com (Christopher McRae)
>
> I don't think the HIDDEN mechanism solves all the problems with our
> current client-server transaction model, however.  I believe that
> browsers will need to provide and advertise a 'callback port' when
> they access certain services.  This would avoid the client having
> to wait and/or poll a server when some request takes a long time to
> process.

Can we please avoid 'callback ports' as they are a real pain through 
firewalls.   Let's just use multithreaded clients instead and just
let that one thread wait until the server is ready.

John Ellson
AT&T Bell Labs