From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: FTP puzzle?
Date: Sun, 07 May 2006 23:03:00 -0000 [thread overview]
Message-ID: <20060507230317.GC5992@trixie.casa.cgf.cx> (raw)
In-Reply-To: <Pine.GSO.4.63.0605071834570.8195@access1.cims.nyu.edu>
On Sun, May 07, 2006 at 06:35:54PM -0400, Igor Peshansky wrote:
>On Fri, 5 May 2006, zzapper wrote:
>>Say I am uploading a very large file to a server, can someone else with
>>an equally fast or slower download start to download before I've
>>finished?
>
>IIRC, the server will report the *actual* size of the file on disk, not
>the "projected" size the file will have after your upload. So anyone
>attempting to download the file before it's finished uploading will get
>a truncated copy.
Personally, I've only tried this with hippos and the resulting carnage
of downloading only .79237 of a hippo convinced me never to try such an
activity again.
cgf
next prev parent reply other threads:[~2006-05-07 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 22:25 zzapper
2006-05-07 22:36 ` Igor Peshansky
2006-05-07 23:03 ` Christopher Faylor [this message]
2006-05-07 23:38 ` Igor Peshansky
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=20060507230317.GC5992@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).