From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) by hurricane.the-brannons.com (Postfix) with ESMTPS id E415277D0D for ; Wed, 23 Dec 2015 07:09:18 -0800 (PST) Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-12v.sys.comcast.net with comcast id x38u1r00B2N9P4d0139VsK; Wed, 23 Dec 2015 15:09:29 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-13v.sys.comcast.net with comcast id x39U1r00T2MDcd70139VEl; Wed, 23 Dec 2015 15:09:29 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.6.0+ Date: Wed, 23 Dec 2015 10:09:28 -0500 Message-ID: <20151123100928.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=1450883369; bh=c83xpH8QuZapA+T/aSD7VMCjYPb9N3H5dGtE7/PwOUo=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=oBCfjE0LclOBqHlv43Uc/tr8SNLmSvW9nSAlkk9l/PjIa+J5GqumWDhE9ZTxNqo+V 0FqYdAaLgjQajWqchSCZFEflNFSZXp/7811VMZkxo0a8HqB0IXpKiSwY/z/oYsLhj7 2+ZQCY3vk2TPmiuK5qeg3OwZQIUUYOpN1cD8xWU5NAAY2VZM60oRE8IYSt/Pg+Ud/w LLz0l0hPKYidkmbdPwU1A3IZeCAVRTMUcMBevSAt4sKL2S2wm8+E2YBUohI0Y1DRel qr4WlcwkNVsRnaUUUpbFXkCSUX+hUdag2H+6wCplNZjjx4JCVou/SnK4JSIoq8vFUd 7J4imQwE1VrCA== Subject: [Edbrowse-dev] One program Two processes 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: Wed, 23 Dec 2015 15:09:19 -0000 this is an incremental step. Moving towardes a merged solution with one instance of curl, one set of cookies etc, there is now just one executable, edbrowse, which runs as either edbrowse or edbrowse-js depending on its name. Like gawk and awk in /bin So still two processes, same interface, same pipes and messages, same communication, but one target that is linked to both names. Eventually edbrowse will spin off js as a thread, not a fork exec of the same program under a different name, and then we won't have to worry about replicating or losing cookies etc. Will also smooth out the differences between linux and windows, which are considerable any time you say the words fork exec. Chris I have not touched CMakeLists, could you modify it to behave the way the makefile does, i.e. no edbrowse.lib and cp edbrowse edbrowse-js We have to copy in windows I suppose, no symbolic link, but this is all temporary anyways, as we eventually won't need edbrowse-js, so no matter. Karl Dahlke