On Saturday, September 1, 2001, at 09:00 AM, Graham Leggett wrote:
Chuck Murcko wrote:
If it's really a stream, and there's no Content-Length (there can't be) then we really need to do a bit more.
Typically if there is no content length then the cache backend modules will ignore that content for this exact reason.
Right, but consider delivering streaming content through a proxy, as opposed to just being an HTTP-cpmpliant proxy. That expands the problem and the solution a bit.
One of the ways is to buffer some determinate (configurable) amount of the stream, as long as at least one client is accessing it. This solves the general case of what I think the original question was about, the scaling problem.
Chuck Murcko Topsail Group http://www.topsail.org/
