From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Ports
Date: Wed, 30 Dec 2015 12:57:42 -0500 [thread overview]
Message-ID: <20151130125742.eklhad@comcast.net> (raw)
Just thinking about ports, in regards to sockets.
I don't know if it's the best way, but the easiest way is to decide
somewhat arbitrarily that edbrowse will use the ports between 47380 and 47390, or some such range.
Microsoft did that when they first came out with their sql server,
if you want to connect to it through odbc you just know it's 3280, or some such
I don't remember the numbers but I use to know.
And being microsoft it became the standard, of course,
so now nobody else touches those ports.
And if they do you can change them in the MS SQL configuration.
So I was thinking edbrowse might use a preset range of ports for its IPC,
and that range could be changed in .ebrc.
Karl Dahlke
next reply other threads:[~2015-12-30 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:57 Karl Dahlke [this message]
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
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=20151130125742.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).