From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) by hurricane.the-brannons.com (Postfix) with ESMTPS id AF49D791EB for ; Fri, 1 Jan 2016 11:05:04 -0800 (PST) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-07v.sys.comcast.net with comcast id 0j4w1s0012VvR6D01j5bRZ; Fri, 01 Jan 2016 19:05:35 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-19v.sys.comcast.net with comcast id 0j5a1s00P2MDcd701j5bhv; Fri, 01 Jan 2016 19:05:35 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151130170044.eklhad@comcast.net> <20160101182449.GB12402@122oven.adamthompson.me.uk> User-Agent: edbrowse/3.6.0+ Date: Fri, 01 Jan 2016 14:05:34 -0500 Message-ID: <20160001140534.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1451675135; bh=PH4xJgJ6ovCUJM0LFn/rHJaP2FywRaTC76kWzSHUdD8=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=vuE0cYOvkldLPsxqDkoFApGu6q039Ct9q0mc1Qhuf8dWZxTV4uahl0FDtkgWkhY36 qMs3EtnCklK0nJMK85T205e2tG3SUJuuZh7zoMBv0Z2GTglsBG/L4s0GFwg56g97cz /r5oDFOeY690enJLyzsQzBJpTNuVFNQ4kBGY6xbLS21reHxU92eA/OEc9JtJ+ylO0u YODTObpORuuXbzDnoUPgoiARM+l1p/rA9SFaA1RkO9LKDefLxe775zzvghwdJrpltl vPRG5UsW7DY7MqZIz+6ITCcb1pJg3NWmbqSAKXvdU1T1Mo0+KnjGACZIJdz5DlxZxb +AXe7JzJKbSFQ== Subject: [Edbrowse-dev] Messages to and from edbrowse-curl X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jan 2016 19:05:04 -0000 > Yeah that makes sense actually, but what do we do with the download > in the meantime? > I'm not sure if we should just pause waiting or not. No I don't think that's good. Servers will time out etc. Nor do I think we should start writing to a temp file and move data around later. I can tell you what we do today and hope that helps. I analyze the headers as they come in and compare them against standards and plugins etc. If it is not text, and not something you know you want to download to play as a plugin, say usually some kind of binary, then I stop the download after the headers, as though it were a HEAD call. There's a curl command to stop the download gracefully. Once I know where to send the data, I restart the call. I get the headers and the data and into the file it goes and it all works without trouble. I imagine edbrowse-curl would analyze the headers as we do now, and if a potential download, it sends the message back to edbrowse and stops. Then edbrowse sends message back restarting the download into the designated file, thus the different messages: fetch generic and fetch into a named file. Sure, I'll work on some different progress options, including quiet, no progress indicators at all, just the file size when done. I'm happy to work on little features in parallel, and there seems to be plenty of them. cheers. Karl Dahlke