- From: Gregory J. Woodhouse <gjw@wnetc.com>
- Date: Thu, 17 Jul 1997 15:47:13 -0700 (PDT)
- To: rlgray@raleigh.ibm.com
- Cc: HTTP Working Group <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Hmm...It seems to me that the only scenario where an extra round trip is unavoidable is a client which is unwilling to wait for a 100 response but which wishes to send a chunked PUT or POST. Since both of these features are new in HTTP/1.1 this seems like it would be a very unusual situation, and in this case I'm not sure an extra round trip would be such a bad thing. To me, it seems like the real problem is that the server has no way of knowing how much data to expect. Accepting a chunked PUT or POST is an all or nothing type of commitment. I doubt it's possible in HTTP/1.1, but it seems to me that the server need to be able to indicate how much data it is willing to accept and then allow the client to decide whether or not to attempt to send the request. (A client may not know how much data it has to send, but it may know that it will not exceed a certain threshold.) --- Gregory Woodhouse gjw@wnetc.com / http://www.wnetc.com/home.html If you're going to reinvent the wheel, at least try to come up with a better one.
Received on Thursday, 17 July 1997 15:59:41 UTC