On Sun, 28 May 2000, Andrew M. Bishop wrote: > > BTW, you are confusing Pipelining with Persistance, you need to sort that > > out to make correct sense of the RFC.
> I know that they are different, but they are not independant. You > cannot do pipelining if the connection is not persistent. If a server You can do it, it should result in the extra pipelined requests being ignored if the server does not support it. It should not result in data corruption! > I believe that this is the sort of thing that the HTTP/1.1 RFC is > talking about when it says: As I said, I don't think this block includes corrupt or short replies. That would imply that the RFC recommends you start transfering a large file, get to the end, realize the server is broken, then restart from the beginning (HTTP/1.0 servers do not support range) and transfer the whole thing again. Clearly this is not workable. > Section 19.6.2 does not say that you can pipeline at all. It does not say you cannot pipeline, it doesn't even mention it! It simply says persistance with old servers must be negotiated, which APT does. The paragraph is talking about how to make use of persistant connection features in old servers in a manner that is still compatible with HTTP/1.1. Jason
