Roger Pantos wrote:
> Server actions include making content available in a specific form at
> a specific time in a specific sequence, and keeping it available for a
> specific time. Client actions include discovering that content is
> available, checking for new content at specific times, what to do if
> none is found, and when it should assume that found content is no
> longer available. Following the specifications of these actions is
> critical. If they are not followed the server and client will not
> interoperate.
What part of that cannot be done in the same way over FTP, SCP, NFS,
or any other protocol for serving files which supports the essential
features, namely range requests?
In other words, in what way does it depend on HTTP, other than the
fact it runs over HTTP because the specification says it must?
-- Jamie