humanize "github.com/dustin/go-humanize"
	"github.com/minio/madmin-go/v3"
	"github.com/minio/minio/internal/logger"
	"github.com/minio/mux"
	"github.com/minio/pkg/v3/policy"
)

const (
	// As per AWS S3 specification, 20KiB policy JSON data is allowed.
	maxBucketPolicySize = 20 * humanize.KiByte

	// Policy configuration file.
	bucketPolicyConfig = "policy.json"
)

    @Test
    @DisplayName("Test wire format structure matches SMB2 specification")
    void testWireFormatStructure() {
        byte[] buffer = new byte[256];
        Arrays.fill(buffer, (byte) 0xCC); // Fill with pattern to detect unwritten areas

        int written = request.writeBytesWireFormat(buffer, 0);

        // Verify structure according to SMB2 CLOSE specification
        // Structure Size (2 bytes) - should be 24

    private static URLStreamHandlerFactory factory;

    private final CIFSContext transportContext;

    /**
     * Sets the URL stream handler factory for the environment. This
     * allows specification of the factory used in creating underlying
     * stream handlers. This can be called once per JVM instance.
     *
     * @param factory
     *            The URL stream handler factory.
     */

        @Test
        void rootUrlIsRoot() throws Exception {
            DummySmbResourceLocator root = new DummySmbResourceLocator("smb://server/");
            // last component includes trailing slash per specification
            assertEquals("server/", root.getName());
            assertEquals("smb://", root.getParent());
            assertTrue(root.isRoot());
        }

        @Test

Un `Request` a également un `request.receive`, qui est une fonction pour « recevoir » le corps de la requête.

Le `dict` `scope` et la fonction `receive` font tous deux partie de la spécification ASGI.

Et ces deux éléments, `scope` et `receive`, sont ce dont on a besoin pour créer une nouvelle instance de `Request`.

#### « Schéma » d’API { #api-schema }

Ici, [OpenAPI](https://github.com/OAI/OpenAPI-Specification) est une spécification qui dicte comment définir le schéma de votre API.

Cette définition de schéma inclut les chemins de votre API, les paramètres possibles qu’ils prennent, etc.

#### « Schéma » de données { #data-schema }

META-INF/MANIFEST.MF Manifest-Version: 1.0 Implementation-Title: maven-wrapper Implementation-Version: 0.5.6 Archiver-Version: Provisio Archiver Built-By: manfred Specification-Title: maven-wrapper Implementation-Vendor-Id: io.takari Created-By: Takari Inc. Build-Jdk: 1.8.0_232 Specification-Version: 0.5.6 META-INF/maven/io.takari/maven-wrapper/pom.properties version=0.5.6 groupId=io.takari artifactId=maven-wrapper org/apache/maven/wrapper/BootstrapMainStarter.class package org.apache.maven.wrapper;...

A "schema" is a definition or description of something. Not the code that implements it, but just an abstract description.

#### API "schema" { #api-schema }

In this case, [OpenAPI](https://github.com/OAI/OpenAPI-Specification) is a specification that dictates how to define a schema of your API.

This schema definition includes your API paths, the possible parameters they take, etc.

#### Data "schema" { #data-schema }

/// info

As this is a WebSocket it doesn't really make sense to raise an `HTTPException`, instead we raise a `WebSocketException`.

You can use a closing code from the [valid codes defined in the specification](https://tools.ietf.org/html/rfc6455#section-7.4.1).

///

### Try the WebSockets with dependencies { #try-the-websockets-with-dependencies }

Run your application:

<div class="termy">

///

## Преимущества стандартизации, альтернативная документация { #standards-based-benefits-alternative-documentation }

Поскольку сгенерированная схема соответствует стандарту [OpenAPI](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md), её можно использовать со множеством совместимых инструментов.