edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Ports
Date: Fri, 1 Jan 2016 14:22:38 +0000	[thread overview]
Message-ID: <20160101142238.GB24842@122oven.adamthompson.me.uk> (raw)
In-Reply-To: <20151130220528.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

On Wed, Dec 30, 2015 at 10:05:28PM -0500, Karl Dahlke wrote:
> I know about domain sockets, but heard they were not available on windows.
> If they were then we could create various /tmp/.edbrowse/sockets
> and bounce through those.

That's my thoughts also. I seem to remember Windows had something like them or
at least some other method of IPC which doesn't involve network ports.
I'm not particularly comfortable with ports tbh.
I suspect whatever we do will have to have some differences between Unix and
Windows, hence why I'd like a more generic IPC interface.

Cheers,
Adam.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-01-01 14:22 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 [this message]
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
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=20160101142238.GB24842@122oven.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).