From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4cb:c000::1]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 1D97F77DC1 for ; Fri, 1 Jan 2016 11:31:31 -0800 (PST) From: Chris Brannon To: edbrowse-dev@lists.the-brannons.com References: <20151130125742.eklhad@comcast.net> <20160101185027.GC12402@122oven.adamthompson.me.uk> <20160001141111.eklhad@comcast.net> Date: Fri, 01 Jan 2016 11:32:02 -0800 In-Reply-To: <20160001141111.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 01 Jan 2016 14:11:11 -0500") Message-ID: <87poxlayfh.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] Ports 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: Fri, 01 Jan 2016 19:31:31 -0000 Karl Dahlke writes: > but if we spin up one curl server per user, > it has to listen on a per-user edbrowse port, > so that's a bit more complicated. Yes, it's terribly complicated, and this is just the sort of scenario for which Unix-domain sockets were designed. I'd say use Unix domain sockets on Unix and Mac, and IP sockets with loopback on Windows, unless there's an implementation of Unix domain sockets for Windows. In any case, we only care about the socket type when it is created and bound or connected. I.E., the socket(), bind(), and connect() calls. So most of the time nobody needs to care whether it is an IP socket or a Unix domain socket. -- Chris