From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hget
Date: Mon, 29 Mar 2004 21:12:48 +0100 [thread overview]
Message-ID: <00a2104440670cbbedfa015c194ac561@vitanuova.com> (raw)
In-Reply-To: <40687E22.2010506@swtch.com>
> it won't work if the connection gets halfway done, hangs up,
> and the remote server doesn't support content-range requests.
> but how often are you in this situation?
actually, it seems (from the hget code) that the server can return
error 206 (partial content) which causes a seek on the output, even if
the content-range request is supported. i've no idea how common this
is though.
i was thinking of changing hget so that if it's writing to stdout, it
would give up with an error rather than trying to seek back and try
again.
the would at least mean you could use it in a pipeline without
worrying about occasionally duplicated portions of output.
an option similar to -o but without the modification time semantics
could yield the current behaviour (ideally, i'd make the modification
time stuff a separate option (-u?) and use it in addition to -o to
get the current -o semantics; but that would break some things).
next prev parent reply other threads:[~2004-03-29 20:12 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 0:58 [9fans] rio and acme scrolling Micah Stetson
2004-03-27 1:51 ` Russ Cox
2004-03-27 5:07 ` Micah Stetson
2004-03-27 15:01 ` David Presotto
2004-03-27 15:07 ` Sape Mullender
2004-03-27 15:12 ` David Presotto
2004-03-27 20:58 ` Derek Fawcus
2004-03-27 15:22 ` Richard Miller
2004-03-27 15:36 ` Sape Mullender
2004-03-27 15:38 ` David Presotto
2004-03-27 15:38 ` Russ Cox
2004-03-27 17:03 ` Richard Miller
2004-03-27 16:07 ` andrey mirtchovski
2004-03-27 20:11 ` Micah Stetson
2004-03-27 20:45 ` thinkpads (was Re: [9fans] rio and acme scrolling) Axel Belinfante
2004-03-28 11:07 ` [9fans] rio and acme scrolling matt
2004-03-29 15:18 ` splite
2004-03-27 20:27 ` Micah Stetson
2004-03-27 23:57 ` Micah Stetson
2004-03-27 3:14 ` jmk
2004-03-27 10:21 ` a
2004-03-27 10:50 ` Dave Lukes
2004-03-29 13:41 ` blstuart
2004-03-29 14:33 ` Russ Cox
2004-03-29 14:36 ` matt
2004-03-29 15:57 ` Axel Belinfante
2004-03-29 17:31 ` Axel Belinfante
2004-03-29 18:42 ` [9fans] hget rog
2004-03-29 19:50 ` Russ Cox
2004-03-29 20:12 ` rog [this message]
2004-03-29 20:16 ` Russ Cox
2004-03-29 20:40 ` rog
2004-03-29 20:42 ` Russ Cox
2004-03-29 21:12 ` rog
2004-03-29 22:23 ` Charles Forsyth
2004-03-29 21:36 ` rog
2004-03-29 23:39 ` Charles Forsyth
2004-03-29 22:48 ` rog
2004-03-29 21:46 ` boyd, rounin
2004-03-29 23:01 ` rog
2004-03-29 22:17 ` boyd, rounin
2004-03-29 23:34 ` rog
2004-03-29 22:49 ` boyd, rounin
2004-03-30 10:19 ` Steve Simon
2004-03-30 0:02 ` Charles Forsyth
2004-03-29 23:22 ` rog
2004-03-29 19:58 ` David Tolpin
2004-03-29 20:08 ` David Tolpin
2004-03-29 20:18 ` rog
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00a2104440670cbbedfa015c194ac561@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).