Chuck Murcko wrote: > 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.
What is the difference between a "proxy" and an "HTTP compliant proxy"?
I only know about HTTP compliant proxies.
> 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.
A stream by it's nature is exactly that - a stream. It cannot be cached
because different requests for the same stream will result in different
content each time.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
