From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Ports
Date: Fri, 01 Jan 2016 11:32:02 -0800 [thread overview]
Message-ID: <87poxlayfh.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160001141111.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 01 Jan 2016 14:11:11 -0500")
Karl Dahlke <eklhad@comcast.net> 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
next prev parent reply other threads:[~2016-01-01 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:57 Karl Dahlke
2015-12-31 2:54 ` Chris Brannon
2015-12-31 3:05 ` Karl Dahlke
2016-01-01 14:22 ` Adam Thompson
2016-01-01 15:01 ` Karl Dahlke
2016-01-01 18:50 ` Adam Thompson
2016-01-01 19:11 ` Karl Dahlke
2016-01-01 19:32 ` Chris Brannon [this message]
2016-01-01 19:09 ` Geoff McLane
2016-01-01 19:31 ` Adam Thompson
2016-01-01 19:38 ` Karl Dahlke
2015-12-31 3:34 ` Karl Dahlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poxlayfh.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).