import com.google.common.cache.CacheBuilder;

import jakarta.annotation.PostConstruct;

/**
 * Helper class for managing crawling configurations.
 * Provides functionality to store, retrieve, and manage different types of crawling configurations
 * including web, file, and data configurations. Supports caching and session-based configuration management.
 */
public class CrawlingConfigHelper {

    /**

     * but an implemantation that encorporates the transport header(for
     * efficiency) might use a different initial bufferIndex. For example,
     * to eliminate copying data when writing NbtSession data one might
     * manage that 4 byte header specifically and therefore the initial
     * bufferIndex, and thus headerStart, would be 4).(NOTE: If one where
     * looking for a way to improve perfomance this is precisly what you

            verify(transportPool).getChallenge(context, address);
            verify(transportPool).logon(context, address);
        }

        @Test
        @DisplayName("Should manage multiple transport types")
        void testMultipleTransportTypes() throws Exception {
            // Given
            SmbTransport sharedTransport = mock(SmbTransport.class);

 * and data sources based on the configured crawling settings.
 *
 * <p>The job supports selective crawling by specifying configuration IDs for different
 * types of crawlers (web, file, data). It manages the crawler process lifecycle,
 * handles timeout scenarios, and ensures proper cleanup of resources.</p>
 *
 * <p>Key features:</p>
 * <ul>
 *   <li>Concurrent crawler process management with configurable limits</li>

     * call, so we can't assume that writes to the Entry have been safely published by some other
     * synchronization actions.)
     *
     * All that said: I haven't actually managed to make this particular test produce a TSAN error
     * for the field accesses in MapIteratorCache. This test *has* found other TSAN errors,

- SSE-C is hardly adopted by most widely used applications, applications prefer server to manage the keys via SSE-KMS or SSE-S3.
- MinIO recommends applications to use SSE-KMS, SSE-S3 for simpler, safer and robust encryption mechanism for replicated buckets.

## Explore Further

/**
 * Base class for implementing services that can handle {@link #doStart} and {@link #doStop}
 * requests, responding to them with {@link #notifyStarted()} and {@link #notifyStopped()}
 * callbacks. Its subclasses must manage threads manually; consider {@link
 * AbstractExecutionThreadService} if you need only a single execution thread.
 *
 * @author Jesse Wilson
 * @author Luke Sandberg
 * @since 1.0
 */
@GwtIncompatible

                    break;
                }
                curReq = next;
                curResp = next.getResponse();
            }
        }
    }

    /**
     * Sends a request and manages the response handling.
     *
     * @param <T> the response type
     * @param request the request to send
     * @param response the response object to populate

import com.orangesignal.csv.CsvConfig;
import com.orangesignal.csv.CsvReader;
import com.orangesignal.csv.CsvWriter;

import jakarta.annotation.Resource;

/**
 * Service class that manages crawling information and parameters.
 * This service provides CRUD operations for crawling sessions and their associated parameters,
 * including session management, cleanup operations, and CSV import/export functionality.
 */

import org.opensearch.index.query.QueryBuilders;

/**
 * Implementation of IndexUpdateCallback that handles file list index updates with concurrent processing.
 * This callback processes file events (create, modify, delete) and manages document indexing and deletion
 * operations in the search engine. It supports recursive crawling with configurable depth and access count limits.
 *