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 739E977D0D for ; Sat, 26 Dec 2015 07:23:23 -0800 (PST) Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-03v.sys.comcast.net with comcast id yFPQ1r0032Udklx01FPgxH; Sat, 26 Dec 2015 15:23:40 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-18v.sys.comcast.net with comcast id yFPg1r0042MDcd701FPghp; Sat, 26 Dec 2015 15:23:40 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151123100928.eklhad@comcast.net> <20151226151049.GC3144@hob.adamthompson.me.uk> User-Agent: edbrowse/3.6.0+ Date: Sat, 26 Dec 2015 10:23:40 -0500 Message-ID: <20151126102340.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=1451143420; bh=/EPbuMv5cO6w98kPs2iWs6BNVNAk4xBHJPbibRFGMrg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=pf1VStSfMSWf949r4QjUNXV1a10pEe39P1hmIOkjuMWSmi3LwZRIg8SAf7KfNCEIn vihY7JrzSH8QATIQZ7jMzeOClrl4iyeAwdnkHVATXadOvArxz4laZdkPHgO+K+k2pf QxeTFSgXO+nMczTUXah31qUwyJDfiZVvxNixrsPujaCOMhxUpdzUR/+sJ+nOAabcYP E+/VsDaJ2VrJrZpwJvfIzOAjQ7t5O9ZA06HU+/cmW0AyX0zEPU0EsgVUCGwV6pkqTt WKE190QJSXWxN6CMKAe4SP8A2dvC3n9xTDBr0OGJZ1gSW3hn8C1XScSrPWyApotZ/x WgswABtVzpKJw== 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 15:23:23 -0000 > I'd go for UDP rather than TCP for local IPC, Imagine one edbrowse-ht process, the one with the curl space, that does all the http https and ftp fetches. edbrowse connects to edbrowse-ht and says "fetch this big http file and return it to me, don't just download it I want it in memory, so return it to me." edbrowse-ht pulls down a hundred meg file and sends it back to edbrowse over socket, but we need perfect fidelity here, we need the continuity and certainty of the stream. If we don't use tcp we'll have to reinvent most of it, so we may as well use tcp, at least for this instance and probably for most of our communications. udp is fine for packet voice and such in that if you miss some packets you don't care, it's barely a click in the sound, but here we need all the bits in exactly the right order. Karl Dahlke