From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Ports
Date: Fri, 01 Jan 2016 14:11:11 -0500 [thread overview]
Message-ID: <20160001141111.eklhad@comcast.net> (raw)
In-Reply-To: <20160101185027.GC12402@122oven.adamthompson.me.uk>
> Ok, I'd feel slightly better about this if there was a way to make the port
> selection automatic rather than configured,
> it feels like multi-user would break in exciting ways otherwise.
Oops, you're right.
I had the model of one edbrowse-curl daemon serving all, and then sure it could listen
on the edbrowse-curl port, whatever that is, and all good,
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.
We'll give this more thought / discussion.
Karl Dahlke
next prev parent reply other threads:[~2016-01-01 19:10 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 [this message]
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=20160001141111.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).