@Test
        @DisplayName("Should create appropriate response")
        void testCreateResponse() {
            Smb2ReadResponse response = request.createResponse(mockContext, request);
            assertNotNull(response);
            assertTrue(response instanceof Smb2ReadResponse);
        }

        @Test
        @DisplayName("Should create response with same configuration and buffer")

    public String boost;

    /** Availability status of the configuration */
    public String available;

    /** Sort order for the configuration */
    public String sortOrder;

    /** User who created the configuration */
    public String createdBy;

    /** Creation timestamp of the configuration */
    public String createdTime;

    /** Version number of the configuration */
    public String versionNo;

						<la:option value="filename.desc">
							<la:message key="labels.search_result_sort_filename_desc" />
						</la:option>
						<la:option value="created.asc">
							<la:message key="labels.search_result_sort_created_asc" />
						</la:option>
						<la:option value="created.desc">
							<la:message key="labels.search_result_sort_created_desc" />
						</la:option>
						<la:option value="content_length.asc">

 * the HTTP message.
 *
 * This class tracks header values line-by-line. A field with multiple comma- separated values on
 * the same line will be treated as a field with a single value by this class. It is the caller's
 * responsibility to detect and split on commas if their field permits multiple values. This

            throw new AssertionError("Failed to create SMB URL: " + spec, e);
        }
    }

    // Utility to build a minimal locator for connect tests
    private static SmbResourceLocatorImpl newLocator(CIFSContext ctx) {
        return new SmbResourceLocatorImpl(ctx, smbUrl("smb://server/share"));
    }

    @Test
    @DisplayName("Constructor with CIFSContext: creates instance")

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

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

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

In your **FastAPI** application, create a `websocket`:

{* ../../docs_src/websockets/tutorial001.py hl[1,46:47] *}

/// note | Technical Details

You could also use `from starlette.websockets import WebSocket`.

     */
    protected interface DefaultQueryBuilderFunction {
        /**
         * Applies the function to create a query builder for the specified field and boost.
         * @param field The field name.
         * @param boost The boost value.
         * @return The created query builder.
         */
        QueryBuilder apply(String field, float boost);
    }

        data: {
          queryId: $queryId.val()
        }
      })
        .done(function(data) {
          var $favorited,
              $favoritedCount;
          if (data.result === "created") {
            $favorited = $favorite.siblings(".favorited");
            $favoritedCount = $(".favorited-count", $favorited);
            $favoritedCount.css("display", "none");

As said in the section [Alternatives](alternatives.md){.internal-link target=_blank}:

<blockquote markdown="1">

**FastAPI** wouldn't exist if not for the previous work of others.

There have been many tools created before that have helped inspire its creation.

I have been avoiding the creation of a new framework for several years. First I tried to solve all the features covered by **FastAPI** using many different frameworks, plug-ins, and tools.

  private final Stats yStats;
  private final double sumOfProductsOfDeltas;

  /**
   * Internal constructor. Users should use {@link PairedStatsAccumulator#snapshot}.
   *
   * <p>To ensure that the created instance obeys its contract, the parameters should satisfy the
   * following constraints. This is the callers responsibility and is not enforced here.
   *
   * <ul>