Re: [9fans] hget

[rog@vitanuova.com]

> unfortunately, it is not in fact guaranteed in practice that the http
> message will have a header that includes a byte count (at all) or an
> accurate one (if that).  hence some of the heuristics.

agreed, but i'd still maintain that it's not good for it to
potentially produce the same data multiple times on an output stream.

in fact it seems to me it should never do this, and doesn't need to:
there's a known point up to which it has good data.  if it has to
refetch data before this point it can just discard it.

getting partial parts of a file there's always a danger that you're a
getting a partial part of a different file, but that case is wrong for
the current hget too (if the new file is shorter you'll get a part of
the older one tacked on to the end, as it doesn't truncate the file
when it seeks to 0).

so maybe that's the right solution: avoid all seeks always; they're never
necessary.

no extra options, and the code should be straightforward.