v7.2.2

Network Binding Improvements

This update enhances the network binding logic, providing more robust handling of port allocation and address binding, especially in scenarios where the default port is unavailable.

Key Changes:

• Explicit Bind Address Handling: The code now explicitly handles cases where a bind address is provided by the user (bind_addr is Some(addr)). It logs the provided address and attempts to bind to it directly.

• Binding to All Interfaces (0.0.0.0) with Fallback: When no bind address is provided (bind_addr is None), the code attempts to bind to all interfaces (0.0.0.0) using the DEFAULT_PORT.

  • Primary Port Binding: The code first attempts to bind to the DEFAULT_PORT. If this succeeds, it logs a success message and proceeds with listening.

  • Alternative Port Binding (Fallback): If binding to the DEFAULT_PORT fails (e.g., the port is already in use), the code now implements a fallback mechanism:

    • It creates a new socket.
    • It attempts to bind to a random available port on all interfaces (using port 0). This ensures that the application can still start even if the default port is occupied.
    • It logs the alternative port that was bound to.

• Logging Improvements: More detailed logging has been added to provide better insight into the binding process, including:

  • Logging the provided bind address (if any).
  • Logging the attempt to bind to all interfaces.
  • Logging success or failure of primary port binding.
  • Logging the alternative port used in the fallback scenario.
  • Logging the final listener address.

• Socket Options: The following socket options are set for improved performance and reliability:

  • set_reuse_address(true): Allows reusing the address immediately after the socket is closed.
  • set_reuse_port(true) (Unix only): Allows multiple sockets to bind to the same port.
  • set_nodelay(true): Disables Nagle's algorithm, reducing latency for small packets.

Benefits:

• Improved Reliability: The fallback to a random port ensures that the application can start even if the default port is in use, increasing its robustness.
• Better Error Handling: The improved logging provides more information for diagnosing binding issues.
• Enhanced Performance: The socket options optimize network communication.
• Clearer Code: The logic is now more structured and easier to understand.