Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 8 of 8 for Broadcast (0.18 sec)

  1. docs_src/websockets/tutorial003_py39.py

                data = await websocket.receive_text()
                await manager.send_personal_message(f"You wrote: {data}", websocket)
                await manager.broadcast(f"Client #{client_id} says: {data}")
        except WebSocketDisconnect:
            manager.disconnect(websocket)
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sat Mar 18 12:29:59 UTC 2023
    - 2.5K bytes
    - Viewed (0)
  2. src/cmd/asm/internal/asm/testdata/amd64error.s

    	// 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"
    Registered: Tue Nov 05 11:13:11 UTC 2024
    - Last Modified: Wed Jun 14 00:03:57 UTC 2023
    - 8.9K bytes
    - Viewed (0)
  3. docs_src/websockets/tutorial003.py

                data = await websocket.receive_text()
                await manager.send_personal_message(f"You wrote: {data}", websocket)
                await manager.broadcast(f"Client #{client_id} says: {data}")
        except WebSocketDisconnect:
            manager.disconnect(websocket)
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Aug 09 13:52:19 UTC 2020
    - 2.5K bytes
    - Viewed (0)
  4. src/cmd/asm/internal/asm/line_test.go

    		{"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`},
    
    Registered: Tue Nov 05 11:13:11 UTC 2024
    - Last Modified: Tue Aug 29 07:48:38 UTC 2023
    - 1.9K bytes
    - Viewed (0)
  5. src/main/java/jcifs/ResolverType.java

    /**
     * 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
    Registered: Sun Nov 03 00:10:13 UTC 2024
    - Last Modified: Sun Jul 01 13:12:10 UTC 2018
    - 1.1K bytes
    - Viewed (0)
  6. src/main/java/jcifs/NameServiceClient.java

         * 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
    Registered: Sun Nov 03 00:10:13 UTC 2024
    - Last Modified: Sun Jul 01 13:12:10 UTC 2018
    - 7.9K bytes
    - Viewed (0)
  7. docs/en/docs/advanced/websockets.md

    ```
    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.
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Oct 06 20:36:54 UTC 2024
    - 6.3K bytes
    - Viewed (0)
  8. src/main/java/jcifs/netbios/UniAddress.java

     * 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
    Registered: Sun Nov 03 00:10:13 UTC 2024
    - Last Modified: Sun Jul 01 13:12:10 UTC 2018
    - 8.3K bytes
    - Viewed (0)
Back to top