From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 60B16787DC for ; Fri, 5 Dec 2014 11:21:38 -0800 (PST) Received: by mail-wi0-f173.google.com with SMTP id r20so2395399wiv.12 for ; Fri, 05 Dec 2014 11:19:55 -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=+HaHFwb5tgdZXHuYdapSyB823jS34pZHLBqA1scGR1k=; b=vRwjJeXk/Scz16H59j9fdTZThG2FDcn26LEmpmpj8BItEkS33BUKMJZs7mMCQ/HJUx spJpPYREVTffGZxEKeiW5//HcBxVF1nHQ2FloMxQvS3yHrrlygbgvhGu1dOwYoC62fGv ukF1k+oMTSwO2P9MOZInSsy7XKGnq5hCGUuqS/7nVA+oSk+ZEFsGeC0XAqR+m/ClGIKl sG6qkqLQB+brh4P4uXsk5tvFuqkw1LowIphGtQYixYjO6wSKhKdJzTPpHyVd6/h8EtpY sVFKRjuT8zMoAfaCiMoot5pTSUniVxj1Ad0Pb6+R3Xh8OtNBWHEuXh/Z/QkRU0Gyi86U yAZg== X-Received: by 10.180.97.195 with SMTP id ec3mr6463932wib.79.1417807195481; Fri, 05 Dec 2014 11:19:55 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id et4sm11172714wjd.15.2014.12.05.11.19.54 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Dec 2014 11:19:54 -0800 (PST) Date: Fri, 5 Dec 2014 19:19:52 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20141205191952.GJ14122@toaster.adamthompson.me.uk> References: <20141104161617.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ah9ph+G2cWRpKogL" Content-Disposition: inline In-Reply-To: <20141104161617.eklhad@comcast.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] - falling behind 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: Fri, 05 Dec 2014 19:21:38 -0000 --Ah9ph+G2cWRpKogL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Dec 04, 2014 at 04:16:17PM -0500, Karl Dahlke wrote: > It might entail a certain amount of redesign, but that's ok. > I'm not even sure javascript existed when I first wrote edbrowse, > so you have to move with the times. > It's a lota lota work, and I don't feel like I could do it myself, > but probably could with some help. I agree, it's going to be a *lot* of work to get things right, but I think it's worth it. One thing I'd really like to accomplish (not sure how yet) is making it so that the js engine can't kill edbrowse totally, i.e. at the moment if js segfaults or goes into an infinite loop that's it, either the browser explodes (in the first case) or you have to manually kill it (using kill or similar) in the second. I've had cases in the past where I've been doing work in one buffer, switched to another to do a bit of research for said work, and boom the whole thing goes away because of some js. This leads me on to my next question; I know we're hoping some day to get a windows port, but does anyone currently use edbrowse on windows and, if thread or process management becomes involved, how much short term effort needs to be made to make things portable (i.e. do we need to look into cross-platform libraries etc)? The reason I ask is that, in order to isolate the js (and potentially other things) from killing the browser, it really needs to run separately with a communication mechanism (this is common practice in modern browsers, with some spawning processes and some using threads I think). Given the state of the code, I suspect processes'd be a bit easier (this is the model used by chrome according to [1]) (chrome is a google packaged version of chromium essentially). Any thoughts? Cheers, Adam. [1] http://blog.chromium.org/2008/09/multi-process-architecture.html --Ah9ph+G2cWRpKogL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUggVYAAoJELZ22lNQBzHOrKgH/29Dtwdy0Nomw0KWNBJWITKU /w/po+tcUoTdrJ8AKAhhEaopSemnpDnJbi5ctK/orS3FJV5Wx2DKVKY40unNenUJ 5aYCn6SDqJbe90029Rulqa3E5tovZxrfTYX7+o29EPWUVFC/yuirz1bbZqRrvmHo wtay2UDpbtkv/AGU6fDGx2yqnuk1x5ORSJlL2dd4YBqcUqqVA+gnl4CE4V0BNkxJ GUrFduDB1XYCy95x0ATLD79spEI6iQooTTRVY5NZ/KQzYjSRbwhMxiNNWEWijc6l 6LEOsYkP/6C3qHQ9OeY6QQ1SowqX3FaZm9j/z28ywxLccCXycH8JIHsMRxuyrkA= =Nm4R -----END PGP SIGNATURE----- --Ah9ph+G2cWRpKogL--