/**
     * The version number of the boost document configuration for optimistic locking.
     * This field is required to prevent concurrent modification conflicts
     * by ensuring the configuration hasn't been modified by another process.
     */
    @Required
    @ValidateTypeFailure
    public Integer versionNo;

    /**
     * The version number of the file authentication configuration for optimistic locking.
     * This field is required to prevent concurrent modification conflicts
     * by ensuring the configuration hasn't been modified by another process.
     */
    @Required
    @ValidateTypeFailure
    public Integer versionNo;

    /**
     * The version number of the file configuration for optimistic locking.
     * This field is required to prevent concurrent modification conflicts
     * by ensuring the configuration hasn't been modified by another process.
     */
    @Required
    @ValidateTypeFailure
    public Integer versionNo;

    /**
     * The version number of the key match configuration for optimistic locking.
     * This field is required to prevent concurrent modification conflicts
     * by ensuring the configuration hasn't been modified by another process.
     */
    @Required
    @ValidateTypeFailure
    public Integer versionNo;

    /**
     * The version number of the web configuration for optimistic locking.
     * This field is required to prevent concurrent modification conflicts
     * by ensuring the configuration hasn't been modified by another process.
     */
    @Required
    @ValidateTypeFailure
    public Integer versionNo;

  /**
   * Notifies the listener that a removal occurred at some point in the past.
   *
   * <p>This does not always signify that the key is now absent from the cache, as it may have
   * already been re-added.
   */
  // Technically should accept RemovalNotification<? extends K, ? extends V>, but because
  // RemovalNotification is guaranteed covariant, let's make users' lives simpler.

 */
public interface SmbTreeHandleInternal extends SmbTreeHandle {

    /**
     * Releases this tree handle back to the pool for reuse
     */
    void release();

    /**
     * Ensures that DFS referrals have been resolved for this tree
     * @throws SmbException if an SMB-specific error occurs
     * @throws CIFSException if a general CIFS error occurs
     */
    void ensureDFSResolved() throws CIFSException;

    /**

/**
 * Interface for transport response messages.
 * This interface represents responses received from network transports.
 */
public interface Response extends Message {

    /**
     * Checks if the response has been received.
     *
     * @return whether the response is received
     */
    boolean isReceived();

    /**
     * Set received status
     */
    void received();

    /**

# Extra Data Types { #extra-data-types }

Up to now, you have been using common data types, like:

* `int`
* `float`
* `str`
* `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.

/**
 * Response for SMB1 TRANS_TRANSACT_NAMED_PIPE transaction.
 *
 * This response contains the data returned from the named pipe
 * after a transact operation (write then read) has been completed.
 */
public class TransTransactNamedPipeResponse extends SmbComTransactionResponse {

    private final byte[] outputBuffer;

    /**
     * Constructs a response for a named pipe transaction.
     *