# ADR-0002 - Avoid using Java serialization

## Status

- ACCEPTED on 2023-12-01

## Context

In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc.
Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:

- **Performance:**
Java's built-in serialization mechanism is often slower compared to other serialization solutions.

And if you declared a `response_model`, it will still be used to filter and convert the object you returned.

**FastAPI** will use that *temporal* response to extract the cookies (also headers and status code), and will put them in the final response that contains the value you returned, filtered by any `response_model`.

You can also declare the `Response` parameter in dependencies, and set cookies (and headers) in them.

# ringbuffer

        // Test subCommand property
        assertEquals(SmbComTransaction.TRANS2_SET_FILE_INFORMATION, response.getSubCommand());

        // Test status property - getStatus() is public
        assertEquals(0, response.getStatus());

        // Test numEntries property - getNumEntries() is public
        assertEquals(0, response.getNumEntries());

        CloseableUtil.closeQuietly(responseData);
        httpRequest.abort();
    }

    /**
     * Checks if the HTTP status code indicates a redirect.
     *
     * @param httpStatusCode The HTTP status code to check
     * @return True if the status code indicates a redirect, false otherwise
     */
    protected boolean isRedirectHttpStatus(final int httpStatusCode) {

        assertTrue(res.containsKey("fess_props"));
        assertTrue(res.containsKey("bug_report_props"));
        assertEquals(Integer.valueOf(0), JsonPath.from(response).get("response.status"));
    }

    @Override
    @AfterEach
    protected void tearDown() {
        // do nothing
    }

    @Test
    void crudTest() {
        testRead();
    }

 */
package jcifs.internal.smb2.lease;

/**
 * Defines directory lease state constants for SMB2/SMB3 directory leasing.
 *
 * This class provides constants and utility methods for managing directory lease states
 * in SMB2/SMB3 protocol implementations. Directory leases enable clients to cache
 * directory metadata and reduce network round-trips for directory operations.
 */
public class DirectoryLeaseState {

    /**

///

/// info | Informação

Obviamente, o cabeçalho `Content-Type`, o código de status, etc, virão do objeto `Response` que você retornou.

///

### Documentar no OpenAPI e sobrescrever `Response` { #document-in-openapi-and-override-response }

      .protocols(listOf(protocol))
      .build()

  @Test
  fun largeStatusLine() {
    assumeTrue(protocol == Protocol.HTTP_1_1)

    server.enqueue(
      MockResponse
        .Builder()
        .status("HTTP/1.1 200 ${"O".repeat(256 * 1024)}K")
        .body("I'm not even supposed to be here today.")
        .build(),
    )
    val call = client.newCall(Request(url = server.url("/")))
    assertFailsWith<IOException> {

 * is available before performing a blocking read.
 */
public class TransPeekNamedPipe extends SmbComTransaction {

    private final int fid;

    /**
     * Constructs a TransPeekNamedPipe request to check the status of a named pipe.
     *
     * @param config the SMB configuration
     * @param pipeName the name of the pipe to peek
     * @param fid the file identifier for the pipe
     */