// Encode the full message to set headerStart
        request.encode(buffer, headerStart);

        // Then - verify the body was written correctly
        byte[] pathBytes = TEST_PATH.getBytes(StandardCharsets.UTF_16LE);

        // Verify structure size (9)
        assertEquals(9, SMBUtil.readInt2(buffer, bodyOffset));

        // Verify tree flags (0)

        return buffer[bufferIndex] & 0xFF;
    }

    int type, length;

    /**
     * Writes the packet to the specified byte array in wire format.
     *
     * @param dst the destination byte array to write to
     * @param dstIndex the starting index in the destination array
     * @return the number of bytes written
     */
    public int writeWireFormat(final byte[] dst, final int dstIndex) {

        return shareAccessHint;
    }

    @Override
    protected int writeBytesWireFormat(byte[] dst, int dstIndex) {
        // Lease break notifications are sent by the server, not written by client
        return 0;
    }

    @Override
    protected int readBytesWireFormat(byte[] buffer, int bufferIndex) throws SMBProtocolDecodingException {
        int start = bufferIndex;

    * So, by using FastAPI you are saving development time, bugs, lines of code, and you would probably get the same performance (or better) you would if you didn't use it (as you would have to implement it all in your code)....

- Delivers a complete, valuable change (feature, bug fix, or improvement).
- Has a concise title (e.g., `[S3] Fix bucket policy parsing #1234`) and a summary with context, referencing issues (e.g., `#1234`).
- Contains well-written, logical commits explaining *why* changes were made (e.g., “Add S3 bucket tagging support so that users can organize resources efficiently”).

        }
        return len;
    }

    /**
     * Writes the AndX wire format to buffer
     * @param dst the destination buffer
     * @param dstIndex the starting index
     * @return the number of bytes written
     */
    protected int writeAndXWireFormat(final byte[] dst, int dstIndex) {
        final int start = dstIndex;

## Pre-requisites

- Initially, only **one** of the sites added for replication may have data. After site-replication is successfully configured, this data is replicated to the other (initially empty) sites. Subsequently, objects may be written to any of the sites, and they will be replicated to all other sites.

- **Removing a site** is not allowed from a set of replicated sites once configured.
- All sites must be using the **same** external IDP(s) if any.

            }

            if ((msg.flags & DCERPC_LAST_FRAG) == DCERPC_LAST_FRAG) {
                return off;
            }
            // all fragment but the last get written using read/write semantics
            doSendFragment(out, off, msg.length);
            off += fragSize;
        }
        throw new IOException();
    }

    /**
     * @param msg
     * @param in

	// that is considered for inlining, remember this
	// shard value is the value per drive shard it
	// will vary based on the parity that is configured
	// for the STANDARD storage_class.
	// inlining means data and metadata are written
	// together in a single file i.e xl.meta
	InlineBlockEnv = "MINIO_STORAGE_CLASS_INLINE_BLOCK"

	// Supported storage class scheme is EC
	schemePrefix = "EC"

	// Min parity drives
	minParityDrives = 0

    customarily used for software interchange.

    b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a