Willy Tarreau d69ce1ffbc MEDIUM: sock_inet: implement sock_inet_bind_receiver() ... This function collects all the receiver-specific code from both tcp_bind_listener() and udp_bind_listener() in order to provide a more generic AF_INET/AF_INET6 socket binding function. For now the API is not very elegant because some info are still missing from the receiver while there's no ideal place to fill them except when calling ->listen() at the protocol level. It looks like some polishing code is needed in check_config_validity() or somewhere around this in order to finalize the receivers' setup. The main issue is that listeners and receivers are created *before* bind_conf options are parsed and that there's no finishing step to resolve some of them. The function currently sets up a receiver and subscribes it to the poller. In an ideal world we wouldn't subscribe it but let the caller do it after having finished to configure the L4 stuff. The problem is that the caller would then need to perform an fd_insert() call and to possibly set the exported flag on the FD while it's not its job. Maybe an improvement could be to have a separate sock_start_receiver() call in sock.c. For now the function is not used but it will soon be. It's already referenced as tcp and udp's ->bind().		2020-09-16 22:08:07 +02:00
..
haproxy	MEDIUM: sock_inet: implement sock_inet_bind_receiver()	2020-09-16 22:08:07 +02:00
import	CLEANUP: assorted typo fixes in the code and comments	2020-06-26 11:27:28 +02:00