edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] background list
Date: Tue, 13 Jan 2015 03:43:43 -0800	[thread overview]
Message-ID: <877fwqc3dc.fsf@the-brannons.com> (raw)
In-Reply-To: <20150012185155.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 12 Jan 2015 18:51:55 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> Also not sure at all if the server is terribly happy about a download
> that is paused for more than a couple minutes.

Both ftp and http have mechanisms for resuming a stopped download.
E.G., in http, you can specify a range of bytes to retrieve.
The ftp protocol has had a restart command since RFC 959.
If you use wget for downloading, and you stop a download in the middle,
you can pass --resume to restart it where it left off.
If we were going to implement suspend/resume, we wouldn't just pause the
process with SIGSUSP, we'd terminate it completely, and then restart the
download where it left off, using the appropriate mechanism for the
protocol.  Yep, it's going to add complexity.

The main reason someone would want this feature is intermittent network
connectivity.  It was quite useful back in the days of dialup,
especially when multiple family members shared the same line for voice
and data.  Intermittent connections are still a problem with laptops
that use wifi or cellular tethering.

-- Chris

  reply	other threads:[~2015-01-13 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 23:51 Karl Dahlke
2015-01-13 11:43 ` Chris Brannon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-11 14:11 Karl Dahlke
2015-01-12 22:29 ` Adam Thompson

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=877fwqc3dc.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.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 NNTP newsgroup(s).