From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (75-164-214-250.ptld.qwest.net [75.164.214.250]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 1637B78F3D for ; Tue, 13 Jan 2015 03:46:20 -0800 (PST) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150012185155.eklhad@comcast.net> Date: Tue, 13 Jan 2015 03:43:43 -0800 In-Reply-To: <20150012185155.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 12 Jan 2015 18:51:55 -0500") Message-ID: <877fwqc3dc.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] background list X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2015 11:46:21 -0000 Karl Dahlke 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