# Directory Leasing Feature - Detailed Design Document

## 1. Overview

Directory leasing extends the SMB3 lease concept to directories, enabling client-side caching of directory metadata and change notifications. This significantly improves performance for applications that frequently enumerate directories or monitor directory changes.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.12**: SMB2_CREATE_REQUEST_LEASE_V2 for directories

     */
    public int getShareAccessHint() {
        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 {

        }
    }

    @Nested
    @DisplayName("Concurrency Tests")
    class ConcurrencyTests {

        @Test
        @DisplayName("Should handle concurrent received notifications")
        void testConcurrentReceived() throws InterruptedException {
            int threadCount = 10;
            CountDownLatch startLatch = new CountDownLatch(1);

import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Change Notify request message.
 *
 * This command is used to monitor a directory for changes
 * and receive notifications when modifications occur.
 *
 * @author mbechler
 */
public class Smb2ChangeNotifyRequest extends ServerMessageBlock2Request<Smb2ChangeNotifyResponse> {

    /**
     * Flag to watch the directory tree recursively

    private byte[] contextHandle;

    // Registration flags
    /** No special registration flags */
    public static final int WITNESS_REGISTER_NONE = 0x00000000;
    /** Register for IP address change notifications */
    public static final int WITNESS_REGISTER_IP_NOTIFICATION = 0x00000001;

    // Registration state
    private volatile WitnessRegistrationState state;
    private volatile long lastHeartbeat;

* Descomprimir cuerpos de requests comprimidos con gzip.
* Registrar automáticamente todos los request bodies.

## Manejo de codificaciones personalizadas de request body { #handling-custom-request-body-encodings }

Veamos cómo hacer uso de una subclase personalizada de `Request` para descomprimir requests gzip.

MinIO batch jobs framework also provides

- Retrying a failed job automatically driven by user input
- Monitoring job progress in real-time
- Send notifications upon completion or failure to user configured target

Following YAML describes the structure of a replication job, each value is documented and self-describing.

```yaml
replicate:
  apiVersion: v1

			Description: "comma separated list of Kafka broker addresses",
			Type:        "csv",
		},
		config.HelpKV{
			Key:         KafkaTopic,
			Description: "Kafka topic used for bucket notifications",
			Optional:    true,
			Type:        "string",
		},
		config.HelpKV{
			Key:         KafkaSASLUsername,
			Description: "username for SASL/PLAIN or SASL/SCRAM authentication",
			Optional:    true,

                log.info("Registered for witness notifications: share={}, id={}", shareName, registration.getRegistrationId());
            }).exceptionally(error -> {
                log.error("Failed to register for witness notifications", error);
                return null;
            });

        } catch (Exception e) {
            log.error("Error registering for witness notifications", e);
        }
    }

    /**

This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.

This includes, for example:

* Email notifications sent after performing an action:
    * As connecting to an email server and sending an email tends to be "slow" (several seconds), you can return the response right away and send the email notification in the background.