*   <li>DELETE - Deletes the specified resource.</li>
     *   <li>HEAD - Same as GET but returns only HTTP headers and no document body.</li>
     *   <li>OPTIONS - Returns the HTTP methods that the server supports.</li>
     *   <li>TRACE - Echoes back the received request, used for debugging.</li>
     *   <li>CONNECT - Converts the request connection to a transparent TCP/IP tunnel.</li>
     * </ul>
     */

) {
  fun noContextTakeover(clientOriginated: Boolean): Boolean =
    if (clientOriginated) {
      clientNoContextTakeover // Client is deflating.
    } else {
      serverNoContextTakeover // Server is deflating.
    }

  companion object {
    private const val HEADER_WEB_SOCKET_EXTENSION = "Sec-WebSocket-Extensions"

    @Throws(IOException::class)
    fun parse(responseHeaders: Headers): WebSocketExtensions {

 *
 *
 *  * <b>About NetBIOS:</b> The NetBIOS name
 * service is a dynamic distributed service that allows hosts to resolve
 * names by broadcasting a query, directing queries to a server such as
 * Samba or WINS. NetBIOS is currently the primary networking layer for
 * providing name service, datagram service, and session service to the
 * Microsoft Windows platform. A NetBIOS name can be 15 characters long

        // Test that the constructor initializes the object correctly
        MsrpcShareEnum shareEnum = new MsrpcShareEnum(TEST_SERVER_NAME);
        assertNotNull(shareEnum);

        // Verify the server name is properly formatted with double backslashes
        try {
            Field servernameField = srvsvc.ShareEnumAll.class.getDeclaredField("servername");
            servernameField.setAccessible(true);

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

But it's the simplest way to focus on the server-side of WebSockets and have a working example:

{* ../../docs_src/websockets_/tutorial001_py310.py hl[2,6:38,41:43] *}

## Create a `websocket` { #create-a-websocket }

}

func main() {
	var node, args string

	flag.StringVar(&node, "local-node-name", "", "the name of the local node")
	flag.StringVar(&args, "args", "", "arguments passed to MinIO server")

	flag.Parse()

	localDisks, err := filterLocalDisks(node, args)
	if err != nil {
		log.Fatal(err)
	}

	if len(localDisks) == 0 {

	}

	if err := target.send(eventData); err != nil {
		return err
	}

	// Delete the event from store.
	return target.store.Del(key)
}

// Close - closes underneath connections to NSQD server.
func (target *NSQTarget) Close() (err error) {
	close(target.quitCh)
	if target.producer != nil {
		// this blocks until complete:
		target.producer.Stop()
	}
	return nil
}

### Server Binaries

filename | sha512 hash
-------- | -----------
[kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.31.14/kubernetes-server-linux-amd64.tar.gz) | b3c4ab211476fc9a3a9514eb85ff9f944d0073ddca4ade96387c01629387340d046b0d2dd7f6efb5953d83ef12b64e2939e45f1cf81649028322ef7cb876f171

```

</details>

## 什麼是容器 { #what-is-a-container }

容器（主要是 Linux 容器）是一種非常輕量的方式，用來封裝應用及其所有相依與必要檔案，並讓其與同一系統中的其他容器（其他應用或元件）隔離。

Linux 容器使用與主機（機器、虛擬機、雲端伺服器等）相同的 Linux kernel。這意味著它們非常輕量（相較於完整模擬整個作業系統的虛擬機）。

因此，容器只消耗很少的資源，與直接執行行程相當（而虛擬機會消耗更多）。

容器也有其各自隔離的執行行程（通常只有一個行程）、檔案系統與網路，簡化部署、安全性與開發等。

## 什麼是容器映像 { #what-is-a-container-image }

容器是由容器映像啟動執行的。

                node[_i] = (byte) _src.dec_ndr_small();
            }
        }
    }

    /**
     * Policy handle structure for DCE/RPC operations.
     * Represents a handle to a policy object on the server.
     */
    public static class policy_handle extends NdrObject {

        /**
         * Default constructor for policy_handle.
         */
        public policy_handle() {