From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 552B1786FA for ; Mon, 8 Dec 2014 15:47:41 -0800 (PST) Received: by mail-wg0-f46.google.com with SMTP id x13so4993656wgg.33 for ; Mon, 08 Dec 2014 15:45:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ft1dcxkXLBD50Hj4UVuYEFNTvwkLfJP0SsjMwXE2FlI=; b=b/UFC/G2u/cS3ah9fIfjpUEsLsEUv+ZjQLQP8ffgkHw5WCn9ySBtEAThAVzqh553gS +5sSuGBsOl/M4fvutsOBZEaF3qrXrfTMaVXWhbM1GphyazxcEeCc70eOE5cyPxBcOgBM /L8/B1/O/Xo1Eig+FEwMMpux7wFY5ypkQp3hxDF9XcKssl1CJ20xBPHhQWcyVnOb6pFy 2NlspeIpnsk35CWl72/Msm6AHWs0YtrvWa6Qy/Ofn17C321/YEjJNyUtMBP+Il5mf1Z5 1VH8u7tpCnPtiXgChlACliUvmJcQt+yT06n2Qo8c6scqMtcP8W9eJnarRef/0wqG3Nx9 blvw== X-Received: by 10.180.77.79 with SMTP id q15mr27481115wiw.8.1418082353836; Mon, 08 Dec 2014 15:45:53 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id n3sm58423803wjz.21.2014.12.08.15.45.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Dec 2014 15:45:52 -0800 (PST) Date: Mon, 8 Dec 2014 23:45:50 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20141208234550.GP14122@toaster.adamthompson.me.uk> References: <20141107180243.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pleSNuEbvnUYtMxG" Content-Disposition: inline In-Reply-To: <20141107180243.eklhad@comcast.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] IPC, sooner? 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: Mon, 08 Dec 2014 23:47:41 -0000 --pleSNuEbvnUYtMxG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 07, 2014 at 06:02:43PM -0500, Karl Dahlke wrote: > > Ok, that sounds like a good idea, though the js process's going to have= to have > > some sort of threading if we want to do ajax etc. >=20 > right, but perhaps threading could come later, on the next increment. > I'm thinking of pulling js to its own process, > with an interprocess communication protocol, > between edbrowse and js proc, > that I would present here, first, for review, > but all having the same functionality as today. > Then of course we enhance it, and consider other engines, and such. Ok, would this be launched from edbrowse via fork (thus making another edbr= owse process) or be a totally separate js engine with a DOM perhaps? > > I'd also like to separate out downloading from the network somehow such= that a > > large download doesn't block the entire program. >=20 > I think this is lots of work for little gain. > Remember, everything asynchronous is a potential nightmare. > I can download a 300 mb file and it just doesn't take very long. > I think those features were developed when people were on dial-up connect= ions. > Really by the time I switch to another session to try to do something els= e, > the file would already be downloaded. > Maybe I'm spoiled by a good connection; but that's how it seems to me. > And speeds will only increase. Perhaps, but I've often found myself wishing edbrowse could download in the background (and straight to disk) particularly when trying to download 1 gb= + isos and the like. Sometimes, like when downloading audiobooks (which somet= imes come as large zip files) you can't use something like wget because there's a js-driven bit of logic which bounces your browser to the correct page, and boom, I'm left with a blocked web browser downloading a file which I've= got no idea how big it is (if I forgot to look at the page) and my machine's fairly resource limited by modern standards (only 1 gb of = ram). Anyway, may be that's just me, and is certainly a topic for a different thr= ead, but I don't think asynchronous downloads is an out dated feature, particularly as files will get larger as internet speeds, amounts of ram and disk space all increase. Cheers, Adam. --pleSNuEbvnUYtMxG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUhjguAAoJELZ22lNQBzHOQvgH/iXgGVD8uco6VziOJGUekyU1 Qifhi7Og8LvdPEOijtrOEXcGqVs19NJYHlAwb0xNpbabbn50yhdDsODI+4g1QUEA CLNwiOsBbtlfQW7ZdB3ZPJeSbpoVHCioGarKSKkJmRrLEm86Km/Aba4r0WIZDvSy KBu7lFYw4HKbK18qrj14QoEGVwO9TcTDT2Nf31e6m8E+ApDdcQb6Tc8X+T9aYuEm wIkVuLY8prwAnKcpETnhrRVUrS8V1CEJJHjmbplVI1nn5ZLoVUAF9GZJGtjWna1x bFlO4qLVWJ71xck++2vEf9qldAtlyBIAVl5EaD+qzIdZ7c8/o+fL8ng8+fPoVyA= =LNHm -----END PGP SIGNATURE----- --pleSNuEbvnUYtMxG--