From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 74E487AD5E for ; Wed, 15 Apr 2015 07:25:16 -0700 (PDT) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-10v.sys.comcast.net with comcast id GEQ61q0062GyhjZ01EQFGX; Wed, 15 Apr 2015 14:24:15 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-09v.sys.comcast.net with comcast id GEQE1q00X5LMg2101EQFR0; Wed, 15 Apr 2015 14:24:15 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150315022022.eklhad@comcast.net> <20150415072306.GK9150@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.3+ Date: Wed, 15 Apr 2015 10:24:14 -0400 Message-ID: <20150315102414.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=1429107855; bh=7a4z6EeeoZdbpjnF8dmWYTdPfvg2kS+V0D71eS1qGzM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=l5O6bpw5B9oYgukCHDHz7Bm/DcV4xYyYI1H76Hl3kL6H4odejEAVi7rRkFKMsoQ0+ /MJBMubZPca+2qJ7Pg2wgv6sznN/iADggs6RltxeUM70/9VCltN5sFRoBH8ht8bjks FRamW4YTUzjpxvddPhMf10M3BBz3tGEsmMCR8LjwofUSe2X0qfhwxuDyAXQ2gSBYFX fA93riI2Nf+ISUI7d7+EiCWbdiJ2UP6wk5lPBYDHLM8tVMpMubkRw+6jE4OztjEjUa qNuBtDxsYRUTo/YRtwhXJ068mrRuN0dc2UhE/UYJCNyUi5zDGp8xsanOgQ2+j1ZvEm RgKDXMxVKUycw== Subject: [Edbrowse-dev] Plugin Converters 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: Wed, 15 Apr 2015 14:25:16 -0000 > Cool. Does the outtype work with protocol handlers as well, No, but I don't think that would be hard to do. > Example of scp: protocol fetching a file into the buffer. But this raises the question, shouldn't we handle this natively? Any protocol that means "fetch this file into the buffer so I can manage it" is probably going to be accomplished by invoking a curl command, which means we could do the same thing through the curl library. And we wouldn't be fetching the file into a temp file, then into the buffer, then, most likely, saving it to a file on disk where you really want it; we would use all the existing machinery such as asking you if you want to download it to disk directly, perhaps in the background. scp: is very likely for downloading files, not casual browsing. We already handle ftp sftp ftps tftp in this manner, I would think I should just add scp to the list. Karl Dahlke