* `bool`

But you can also use more complex data types.

And you will still have the same features as seen up to now:

* Great editor support.
* Data conversion from incoming requests.
* Data conversion for response data.
* Data validation.
* Automatic annotation and documentation.

## Other data types { #other-data-types }

Here are some of the additional data types you can use:

* `UUID`:

    public val shutdownOutput: Boolean = false,
  ) : SocketEffect

  /**
   * On HTTP/2, send a [GOAWAY frame](https://tools.ietf.org/html/rfc7540#section-6.8) immediately
   * after the response and will close the connection when the client's socket is exhausted.
   *
   * On HTTP/1 this closes the socket.
   */
  public object ShutdownConnection : SocketEffect

  /**

        if (in.read(buffer, bufferIndex, length) != length) {
            throw new IOException("unexpected EOF reading netbios retarget session response");
        }
        final int addr = readInt4(buffer, bufferIndex);
        bufferIndex += 4;
        retargetAddress = new NbtAddress(null, addr, false, NbtAddress.B_NODE);

	// ErrIncorrectSequence is returned when an out-of-sequence item is received.
	ErrIncorrectSequence = errors.New("out-of-sequence item received")
)

// ErrResponse is a remote error response.
type ErrResponse struct {
	msg string
}

func (e ErrResponse) Error() string {
	return fmt.Sprintf("remote: %s", e.msg)

   readTimeoutMillis, retryOnConnectionFailure, socketFactory, sslSocketFactory, writeTimeoutMillis
 * **PushPromise**: headers, method, path, response
 * **Request**: body, cacheControl, headers, method, url
 * **Response**: body, cacheControl, cacheResponse, code, handshake, headers, message,
   networkResponse, priorResponse, protocol, receivedResponseAtMillis, request, sentRequestAtMillis

        HandleGuid guid = new HandleGuid();

        // Create handle info with empty file ID (will be populated after successful create response)
        HandleInfo info = new HandleInfo(path, guid, new byte[16], type, timeout, leaseKey);

        lock.writeLock().lock();
        try {
            handles.put(path, info);

        setupMockContext();
        Smb2IoctlRequest request = new Smb2IoctlRequest(mockConfig, TEST_CONTROL_CODE, TEST_FILE_ID, TEST_OUTPUT_BUFFER);

        Smb2IoctlResponse response = request.createResponse(mockContext, request);

        assertNotNull(response);
        verify(mockContext).getConfig();
    }

    @Test
    @DisplayName("Test setFlags method")
    void testSetFlags() {
        setupMockConfig();

        }
    }

    private FileEntry advance() throws CIFSException {
        final int n =
                this.response.getStatus() == WinError.ERROR_MORE_DATA ? this.response.getNumEntries() - 1 : this.response.getNumEntries();
        while (this.ridx < n) {
            final FileEntry itm = this.response.getResults()[this.ridx];
            this.ridx++;
            if (filter(itm)) {
                return itm;
            }

 */
package jcifs.internal.smb2.ioctl;

import jcifs.Decodable;
import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Validate Negotiate Info response data structure. This structure contains the server's
 * validation of the originally negotiated SMB2 dialect.
 *
 * @author mbechler
 *
 */
public class ValidateNegotiateInfoResponse implements Decodable {

It is designed to have functions that receive two parameters, one "request" and one "response". Then you "read" parts from the request, and "write" parts to the response. Because of this design, it is not possible to declare request parameters and bodies with standard Python type hints as function parameters.