From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-38-131-64.ptld.qwest.net [71.38.131.64]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 4F11577E8A; Mon, 28 Sep 2015 08:17:00 -0700 (PDT) From: Chris Brannon To: Adam Thompson Cc: Karl Dahlke , ubuntu@geoffair.info, Edbrowse-dev@lists.the-brannons.com References: <20150826100515.eklhad@comcast.net> <20150928044217.GQ2254@toaster.adamthompson.me.uk> Date: Mon, 28 Sep 2015 08:20:18 -0700 In-Reply-To: <20150928044217.GQ2254@toaster.adamthompson.me.uk> (Adam Thompson's message of "Mon, 28 Sep 2015 05:42:17 +0100") Message-ID: <87h9mefu4t.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] edbrowse-js back in the fold?? 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: Mon, 28 Sep 2015 15:17:00 -0000 Adam Thompson writes: >> 5. All of edbrowse is once again a c++ program (a minor nuisance). > > That assumes we stick with our already rather outdated spidermonkey version Any progress with looking into duktape? Would you like me to have a go at it? > I'm not sure about the portability of but I'm not sure that's where we should go either. > I think, if I remember my original design correctly, > I was thinking more of having the DOM in a separate process, > may be even one per browser buffer. We went for just moving the js at the time > because we needed to encapsulate things and allow switching js engines, Yes, this is also how I remember that discussion. > I was thinking, seeing as we need all sorts of networking, > asynchronous processing etc, whether it'd make sense to look at using a library to do this. So how would that look, exactly? > Or head down the above route. I'd also throw out there > that we have web sockets becoming a > progressively larger "thing" in web development, And we also have stuff like HTTP/2 server push coming up on us.