From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 71EFA77C83 for ; Sat, 26 Dec 2015 05:36:19 -0800 (PST) Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-03v.sys.comcast.net with comcast id yDcT1r00527uzMh01DccUQ; Sat, 26 Dec 2015 13:36:36 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-02v.sys.comcast.net with comcast id yDcb1r00W2MDcd701Dcbky; Sat, 26 Dec 2015 13:36:36 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151123100928.eklhad@comcast.net> <20151226091107.GB3144@hob.adamthompson.me.uk> User-Agent: edbrowse/3.6.0+ Date: Sat, 26 Dec 2015 08:36:35 -0500 Message-ID: <20151126083635.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=1451136996; bh=kO915fCY4jaLu5GF853DsPmIIfN1hjNqB7cWMJ+r+Vk=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=WFHcluMMw1gxM4ASNJNfLYdw9Wkkv/GP37GjIzWDa1xxlCbQrPyWzaBYK57+UgthS G9hm9gZQXoxcS2UM7wExKe/Dc51mcwQjijtpAraTo2kwIjiGAJo63UrJ2POhDAdVSD 3Hm7vhx9n413q7HcThP4+XxdOb2ip6EG4pFXzsfJdXeNmmNfipS1mZUiLRSxsBAveu KzDOzU5keQifVTJMdOwXUuFO9cL5pmknftEXCE5mBV8K66py+0gLbrKST9EvfThSPQ ncv9FCFAuIJ5n/VQdNuVJ5Dj6SavMpe3b1mh3K7Uj8YQfPp1b0M5LixJSxkJxXGIlE giznrC3BbTFzg== 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: Sat, 26 Dec 2015 13:36:19 -0000 > I'm also going to look into IPC mechanisms for Windows Geoff says that if you want portable flexible interprocess communication, (more flexible than pipes), you have to bite the bullet and use sockets. Processes listen on certain ports, send messages to each other via tcp, using send() and recv(), which are both unix and windows calls. It's rather a pain to set up initially but when it is rolling it works fine. I'm not looking forward to that, but as I think about itI'm more convinced he's right, and why should I have to think about it at all; he's the expert. He knows. So we may have to bring back tcp.c from the archives of git. This was a wrapper file that set up sockets in a unix / windows hiding fashion, with one common interface. We used it long before curl, when I did it all by hand, then through it away since curl seems to do everything. But here we may need it again so Chris you might want to at least find the latest and clean it up etc. There was also a tcp.h but honestly it was small and I wouldn't mind folding it into eb.h. Karl Dahlke