assertTrue(mockService.processHeartbeat(regId, 1));
        assertTrue(mockService.processHeartbeat(regId, 2));
        assertTrue(mockService.processHeartbeat(regId, 3));

        // 3. Event notifications
        mockService.sendNotification(WitnessEventType.RESOURCE_CHANGE, "\\\\cluster\\share");
        mockService.sendNotification(WitnessEventType.CLIENT_MOVE, "\\\\cluster\\share");

     * Search logs from these bots will be automatically removed.
     */
    @Size(max = 10000)
    public String purgeByBots;

    /**
     * Email addresses to receive system notifications.
     * Multiple addresses can be specified, separated by commas.
     */
    @Size(max = 1000)
    public String notificationTo;

    /**
     * Enable or disable search suggestions based on search logs.

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.

        assertEquals(combinedFilter, readFilter);
        assertEquals(0x1F, readFilter); // 1 + 2 + 4 + 8 + 16 = 31 = 0x1F
    }

    @Test
    @DisplayName("Should handle all file change notifications")
    void testAllFileChangeNotifications() {
        // Given - all possible filters
        int allFilters = Smb2ChangeNotifyRequest.FILE_NOTIFY_CHANGE_FILE_NAME | Smb2ChangeNotifyRequest.FILE_NOTIFY_CHANGE_DIR_NAME

Isso é útil para operações que precisam acontecer após uma request, mas que o cliente não precisa realmente esperar a operação terminar antes de receber a resposta.

Isso inclui, por exemplo:

* Notificações por e-mail enviadas após realizar uma ação:

        mockNotifications.add(fileNotifyInfo1);
        mockNotifications.add(fileNotifyInfo2);
        mockNotifications.add(fileNotifyInfo3);
    }

    /**
     * Test watch() method returning notifications
     */
    @Test
    void testWatch() throws CIFSException {
        // Setup mock behavior
        when(watchHandle.watch()).thenReturn(mockNotifications);

        // Execute

import jcifs.dcerpc.ndr.NdrBuffer;
import jcifs.dcerpc.ndr.NdrException;

/**
 * WitnessRegister RPC message implementation for MS-SWN specification.
 * This message is used to register for witness notifications on a specific resource.
 */
public class WitnessRegisterMessage extends WitnessRpcMessage {

    // Input parameters for WitnessRegister
    private WitnessVersion version;
    private String netName;

        assertNotNull(verifyCacheEntry);
        assertTrue(verifyCacheEntry.isComplete());
        assertEquals(2, verifyCacheEntry.getChildren().size());

        // Step 8: Test change notifications
        // Simulate file addition
        directoryLeaseManager.handleDirectoryChange(directoryPath, "newfile.txt", DirectoryChangeNotifier.DirectoryChangeType.FILE_ADDED);

        // Cache should be invalidated

    }

    // Happy path for SMB2: a response is received and the list is returned; tree is closed
    @Test
    @DisplayName("watch() SMB2 happy path returns notifications and closes tree")
    void watch_smb2_success_returnsList_andClosesTree() throws Exception {
        List<FileNotifyInformation> info = new ArrayList<>();
        NotifyResponse resp = mock(NotifyResponse.class);

Luego tu API (imaginemos):

* Enviará la factura a algún cliente del desarrollador externo.
* Recogerá el dinero.
* Enviará una notificación de vuelta al usuario de la API (el desarrollador externo).
    * Esto se hará enviando un request POST (desde *tu API*) a alguna *API externa* proporcionada por ese desarrollador externo (este es el "callback").