Issues Beyond HTTP/1.1 ???

Issue 1:

When a user stops a transmission, the CGI's generated do not get 
killed. Am I correct to say that this is so because the HTTP protocol
does not contemplate an "transmission interrupted" signal?

Is there any knoen solution known to this problem that does not
involve changes to the protocol?


Issue 2:

Local data shows that our connetions will be swamped by the end of
the year. Caching seems to be a good way to handle this problem.
However, most of the caching schemes in use right now are client side. 
In fact, some forms of traffic can only be efficiently cached
by server inititiated and managed caches (see Push-Caching
http://daisy.uwaterloo.ca/~alopez-o/cspap/cache/Overview.html)


Alex


-- 
Alex Lopez-Ortiz                                       alexlo@opentext.com
Research & Development                               Open Text Corporation
http://daisy.uwaterloo.ca/~alopez-o                     (519)-888-7111x318

Received on Friday, 22 March 1996 11:13:19 UTC