Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: galene@lists.galene.org
Subject: [Galene] Re: About UDP multiplexing
Date: Sun, 23 Mar 2025 10:59:23 +0100	[thread overview]
Message-ID: <874izkjcec.wl-jch@irif.fr> (raw)
In-Reply-To: <91DBD932-2B0A-43D4-8905-EC2886ACA2F4@webweaving.org>

Hi Dirk,

> Or - when nothing is specified —  just use any port above 1024.

That's pretty much what we do.  When nothing is specified, we let the
kernel choose the port every time we need a UDP socket.

> So perhaps it would be nice to simplify this in one option to:
> 
> -udp-range 10000-20000
> -udp-range 10000

I'm not sure what's less confusing: using two mutually exclusive options,
or using a single option that's overloaded (currently, -udp-range does not
enable muxing, it merely restricts the range of ports used for un-muxed
sockets).

OTOH, we'll likely have requests for other functionality (binding to
a single interface, or binding to a single IP address comes to mind), so
perhaps overloading the option will prevent multiplying options in the
future.

I'm also wondering whether we shouldn't move this to data/config.json.
Right now, data/config.json is restricted to options that can be changed
at runtime without restrarting the server, but perhaps it might make sense
to relax this requirement and put everything except debugging options into
the config file.
pp
Does anyone have opinions?

-- Juliusz

  reply	other threads:[~2025-03-23  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 18:29 [Galene] " Juliusz Chroboczek
2025-03-22 20:32 ` [Galene] " Dirk-Willem van Gulik
2025-03-23  9:59   ` Juliusz Chroboczek [this message]
2025-03-23 11:42     ` Dirk-Willem van Gulik
2025-03-30 21:22       ` Juliusz Chroboczek
2025-03-31  4:29         ` Gabriel Pruvost-Kerneis
2025-03-31 11:46           ` Juliusz Chroboczek

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

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874izkjcec.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dirkx@webweaving.org \
    --cc=galene@lists.galene.org \
    /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