}, "Should throw exception for invalid NetBIOS name");
    }

    @Test
    @DisplayName("Should handle broadcast resolution timeout")
    @Timeout(value = 1, unit = TimeUnit.SECONDS) // Very short timeout
    void testBroadcastTimeout() {
        // Configure for broadcast-only resolution with very short timeout
        when(mockConfig.getResolveOrder()).thenReturn(Arrays.asList(ResolverType.RESOLVER_BCAST));

/**
 * Enumeration of usable resolver types
 *
 * @author mbechler
 *
 */
public enum ResolverType {
    /**
     * Resolve using WINS server
     */
    RESOLVER_WINS,

    /**
     * NETBIOS broadcast
     */
    RESOLVER_BCAST,

    /**
     * DNS
     */
    RESOLVER_DNS,

    /**
     * LMHosts file lookup
     */
    RESOLVER_LMHOSTS

     */

    public static final int P_NODE = 1;

    /**
     * Try Broadcast queries first, then try to resolve the name using the
     * nameserver.
     */

    public static final int M_NODE = 2;

    /**
     * A Hybrid node tries to resolve a name using the nameserver first. If
     * that fails use the broadcast address. This is the default if a nameserver

     */

    public static final int P_NODE = 1;

    /**
     * Try Broadcast queries first, then try to resolve the name using the
     * nameserver.
     */

    public static final int M_NODE = 2;

    /**
     * A Hybrid node tries to resolve a name using the nameserver first. If
     * that fails use the broadcast address. This is the default if a nameserver

     * signifies no scope.
     *
     * The additional <code>svr</code> parameter specifies the address to
     * query. This might be the address of a specific host, a name server,
     * or a broadcast address.
     *
     * @param host
     *            the name to resolve
     * @param type
     *            the hex code of the name
     * @param scope
     *            the scope of the name

```
Client #1596980209979 left the chat
```

/// tip

The app above is a minimal and simple example to demonstrate how to handle and broadcast messages to several WebSocket connections.

But keep in mind that, as everything is handled in memory, in a single list, it will only work while the process is running, and will only work with a single process.

                    while (timeout > 0) {
                        response.wait(timeout);

                        /*
                         * JetDirect printer can respond to regular broadcast query
                         * with node status so we need to check to make sure that
                         * the record type matches the question type and if not,
                         * loop around and try again.

        // Check capabilities
        assertTrue(testConfig.getCapabilities() != 0, "Capabilities should be non-zero");

        // Check broadcast address
        assertNotNull(testConfig.getBroadcastAddress());
        assertEquals("255.255.255.255", testConfig.getBroadcastAddress().getHostAddress());

        // Check resolver order

                    while (timeout > 0) {
                        response.wait(timeout);

                        /* JetDirect printer can respond to regular broadcast query
                         * with node status so we need to check to make sure that
                         * the record type matches the question type and if not,
                         * loop around and try again.

        // Then
        assertSame(localAddr, resultLocalAddr, "Should delegate local address");
        assertSame(broadcastAddr, resultBroadcastAddr, "Should delegate broadcast address");
        assertSame(winsServers, resultWinsServers, "Should delegate WINS servers");
        assertEquals(445, resultLocalPort, "Should delegate local port");

        verify(mockDelegate).getLocalAddr();