In the next chapters, I'll give you more **concrete recipes** to deploy FastAPI applications.

But for now, let's check these important **conceptual ideas**. These concepts also apply to any other type of web API. 💡

## Security - HTTPS { #security-https }

In the [previous chapter about HTTPS](https.md) we learned about how HTTPS provides encryption for your API.

    /** All pipe instances are busy */
    int NT_STATUS_PIPE_BUSY = 0xC00000ae;
    /** No process is on the other end of the pipe */
    int NT_STATUS_PIPE_DISCONNECTED = 0xC00000b0;
    /** The pipe is being closed */
    int NT_STATUS_PIPE_CLOSING = 0xC00000b1;
    /** Waiting for a process to open the other end of the pipe */
    int NT_STATUS_PIPE_LISTENING = 0xC00000b3;
    /** The file that was specified is a directory */

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

  - [Changelog since v1.13.11](#changelog-since-v11311)
    - [Other notable changes](#other-notable-changes)
- [v1.13.11](#v11311)
  - [Downloads for v1.13.11](#downloads-for-v11311)
    - [Client Binaries](#client-binaries-1)
    - [Server Binaries](#server-binaries-1)
    - [Node Binaries](#node-binaries-1)
  - [Changelog since v1.13.10](#changelog-since-v11310)
    - [Other notable changes](#other-notable-changes-1)
- [v1.13.10](#v11310)

- **Performance:**
Java's built-in serialization mechanism is often slower compared to other serialization solutions.
This is due to Java's use of reflection and the need to maintain a lot of metadata.

- **Size of Serialized Data:**
Java serialization tends to produce larger serialized objects because it includes class metadata and other overhead.

- **Flexibility and Control:**

   * plus the given elements, according to {@link #expectContents(java.util.Collection)}. In other
   * words, for the default {@code expectContents()} implementation, the number of occurrences of
   * each given element has increased by one since the test collection was created, and the number
   * of occurrences of all other elements has not changed.
   *

And all of them will use the same WebSocket connection.

## Using `Depends` and others { #using-depends-and-others }

In WebSocket endpoints you can import from `fastapi` and use:

* `Depends`
* `Security`
* `Cookie`
* `Header`
* `Path`
* `Query`

They work the same way as for other FastAPI endpoints/*path operations*:

{* ../../docs_src/websockets_/tutorial002_an_py310.py hl[68:69,82] *}

import java.util.concurrent.TimeoutException;
import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;

/**
 * Unit tests for any listenable future that chains other listenable futures. Unit tests need only
 * override buildChainingFuture and getSuccessfulResult, but they can add custom tests as needed.
 *
 * @author Nishant Thakkar
 */
@NullUnmarked
@GwtIncompatible

   * IllegalStateException} if it is accessed in any way, with the following exceptions:
   *
   * <ul>
   *   <li>{@code view.equals(view)} evaluates to {@code true} (but any other {@code equals()}
   *       expression involving {@code view} will throw)
   *   <li>{@code hashCode()} does not throw
   *   <li>if {@code node} is re-added to the network after having been removed, {@code view}'s

        .Builder()
        .add("WWW-Authenticate", "Other abc==")
        .build()
    assertThat(headers.parseChallenges("WWW-Authenticate"))
      .isEqualTo(
        listOf(Challenge("Other", mapOf(null to "abc=="))),
      )
  }

  @Test fun token68AndAuthParams() {
    val headers =
      Headers
        .Builder()
        .add("WWW-Authenticate", "Other abc==, realm=myrealm")
        .build()