From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com, ubuntu@geoffair.info
Subject: [Edbrowse-dev] Ports
Date: Fri, 01 Jan 2016 10:01:35 -0500 [thread overview]
Message-ID: <20160001100135.eklhad@comcast.net> (raw)
In-Reply-To: <20160101142238.GB24842@122oven.adamthompson.me.uk>
> I seem to remember Windows had something like domain sockets or
> at least some other method of IPC which doesn't involve network ports.
I really don't know.
I thought Geoff said traditional sockets were the best, perhaps only
practical form of IPC besides pipes,
but don't want to put words in his mouth so will cc to him.
> I'm not particularly comfortable with ports tbh.
> I suspect whatever we do will have to have some differences between Unix and
> windows.
Connecting using traditional sockets on network ports,
all through loopback, really doesn't bother me at all, if ports can be
reconfigured in .ebrc -
well, doesn't bother me as much as having different systems on the two OSs.
If this is the best / only way for windows,
or even a practical way on windows,
then let's just do it across the board.
We've already confirmed my socket layer works portably across both -
would probably be easy to add in udp capability if needed.
but I'm sure Geoff knows more than I do here. Other practical/flexible IPC
on Windows? Or any issues with loopback sockets in network ports?
Karl Dahlke
next prev parent reply other threads:[~2016-01-01 15:01 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 [this message]
2016-01-01 18:50 ` Adam Thompson
2016-01-01 19:11 ` Karl Dahlke
2016-01-01 19:32 ` Chris Brannon
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=20160001100135.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=ubuntu@geoffair.info \
/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).