public enum RdmaCapability {
    /**
     * Remote direct read operations
     */
    RDMA_READ,

    /**
     * Remote direct write operations
     */
    RDMA_WRITE,

    /**
     * Traditional send/receive with RDMA
     */
    RDMA_SEND_RECEIVE,

    /**
     * Dynamic memory registration
     */
    MEMORY_REGISTRATION,

    /**
     * Fast memory region registration
     */
    FAST_REGISTRATION

         - key: "content-type"
           value: "image/*" # match objects with 'content-type', with all values starting with 'image/'

#    notify:
#      endpoint: "https://notify.endpoint" # notification endpoint to receive job status events
#      token: "Bearer xxxxx" # optional authentication token for the notification endpoint
#
#    retry:
#      attempts: 10 # number of retries for the job before giving up

* Processing data:
    * For example, let's say you receive a file that must go through a slow process, you can return a response of "Accepted" (HTTP 202) and process the file in the background.

## Using `BackgroundTasks` { #using-backgroundtasks }

While the corresponding feature can be changed or dropped without notice, users should receive a notice about the property rename or removal.

Experimental properties MUST NOT be supplemented with command-line options.
They can always be passed via `-D` on the command line.
The feature should leave the experimental stage to receive a build option.

        // Arrange
        when(handle.getReceiveBufferSize()).thenThrow(new CIFSException("receive size failed"));

        // Act + Assert
        CIFSException ex = assertThrows(CIFSException.class, () -> handle.getReceiveBufferSize());
        assertEquals("receive size failed", ex.getMessage());
        verify(handle).getReceiveBufferSize();
    }

    @Test

     */
    int DEFAULT_RESPONSE_TIMEOUT = 30000;
    /**
     * Default socket timeout in milliseconds.
     */
    int DEFAULT_SO_TIMEOUT = 35000;
    /**
     * Default receive buffer size for SMB transport.
     */
    int DEFAULT_RCV_BUF_SIZE = 0xFFFF;
    /**
     * Default send buffer size for SMB transport.
     */
    int DEFAULT_SND_BUF_SIZE = 0xFFFF;
    /**

    }

    /**
     * Constructs an SMB2 IOCTL response with the given configuration and output buffer.
     *
     * @param config the configuration for this response
     * @param outputBuffer the buffer to receive output data
     */
    public Smb2IoctlResponse(final Configuration config, final byte[] outputBuffer) {
        super(config);
        this.outputBuffer = outputBuffer;
    }

    /**

    /**
     * Constructs a TransCallNamedPipeResponse with the specified configuration and output buffer.
     *
     * @param config the SMB configuration
     * @param inB the buffer to receive response data from the named pipe
     */
    public TransCallNamedPipeResponse(final Configuration config, final byte[] inB) {
        super(config);
        this.outputBuffer = inB;
    }

    @Override

     * Constructs a new MsrpcQueryInformationPolicy request.
     *
     * @param policyHandle the policy handle obtained from LsarOpenPolicy
     * @param level the information level to query
     * @param info the NdrObject to receive the policy information
     */
    public MsrpcQueryInformationPolicy(final LsaPolicyHandle policyHandle, final short level, final NdrObject info) {
        super(policyHandle, level, info);
        this.ptype = 0;

- maven-3.10.x — target for 3.x changes (new features + bug fixes).  
  If the change should also go to maven-3.9.x, request a backport in the PR.
  maven-3.9.x should receive only serious bug fixes, as it is approaching EOL.

Backports are typically handled by maintainers; 
however, after agreement you may open a separate backport PR to the target maintenance branch.
-->