// Unsupported broadcast.
	VFPCLASSSD.BCST $0, (AX), K2, K1 // ERROR "unsupported broadcast"
	VFPCLASSSS.BCST $0, (AX), K2, K1 // ERROR "unsupported broadcast"
	// Broadcast without memory operand.
	VADDPD.BCST X3, X2, K1, X1       // ERROR "illegal broadcast without memory argument"
	VADDPD.BCST X3, X2, K1, X1       // ERROR "illegal broadcast without memory argument"

		{"VADDPD.SAE.BCST X0, X1, X2", `can't combine rounding/SAE and broadcast`},
		{"VADDPD.BCST.SAE X0, X1, X2", `can't combine rounding/SAE and broadcast`},
		{"VADDPD.BCST.Z.SAE X0, X1, X2", `Z suffix should be the last; can't combine rounding/SAE and broadcast`},
		{"VADDPD.SAE.SAE X0, X1, X2", `duplicate suffix "SAE"`},
		{"VADDPD.RZ_SAE.SAE X0, X1, X2", `bad suffix combination`},

     */
    int RPC_PT_CO_CANCEL = 0x15;
    /**
     * Orphaned packet type
     */
    int RPC_PT_ORPHANED = 0x16;

    // RPC_C_PF_ flags (packet flags)
    /**
     * Broadcast packet flag
     */
    int RPC_C_PF_BROADCAST = 0x01;
    /**
     * No fragmentation packet flag
     */
    int RPC_C_PF_NO_FRAGMENT = 0x02;
    /**
     * Maybe semantics packet flag
     */

/**
 * 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

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

     * 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

 * and {@link java.net.InetAddress}. The name resolution mechanisms
 * used will systematically query all available configured resolution
 * services including WINS, broadcasts, DNS, and LMHOSTS. See
 * <a href="../../resolver.html">Setting Name Resolution Properties</a>
 * and the <code>jcifs.resolveOrder</code> property. Changing
 * jCIFS name resolution properties can greatly affect the behavior of