[Galene] Re: About UDP multiplexing

[Dirk-Willem van Gulik <dirkx@webweaving.org>]

On 23 Mar 2025, at 10:59, Juliusz Chroboczek <jch@irif.fr> wrote:

>> 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).

So as they are mutually exclusive - I like the explicitness of this.
> 
> 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.

Indeed - and one can go to the common syntax of [[ip][:port][:[ip][:port]].
> 
> 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.


For me; having things that require a restart away from things that don’t (or can be API changed) is goodness.  And generally easier on, for example, the FreeBSD modular conf system. It also conceptually aligns well; as right now things you specify on the command line need to be in sync with other things at OS level (such as firewall ports) - whereas the things in config.json are more private to galene and do not require anyone outside the galene ecosystem to know.

Dw