return URL_QUEUE_THREAD_LOCAL.get();
    }

    /**
     * Sets the URL queue for the current thread. If the provided URL queue is null,
     * the URL queue for the current thread is removed.
     *
     * @param urlQueue the URL queue to be set for the current thread, or null to remove the URL queue
     */
    public static void setUrlQueue(final UrlQueue<?> urlQueue) {
        if (urlQueue == null) {

        final UrlQueue<?> urlQueue = (UrlQueue<?>) objs[1];
        final String url = (String) objs[2];
        final Throwable e = (Throwable) objs[3];
        if (logger.isDebugEnabled()) {
            logger.debug("Child URL: {} from {}", url, urlQueue.getUrl(), e);
        }
    }

    /**
     * Processes child URLs processing exception log events.
     *

    /**
     * Adds a URL to the queue.
     *
     * @param sessionId The session ID.
     * @param url The URL.
     */
    void add(String sessionId, String url);

    /**
     * Inserts a URL queue.
     *
     * @param urlQueue The URL queue.
     */
    void insert(QUEUE urlQueue);

    /**
     * Deletes a URL queue.
     *
     * @param sessionId The session ID.

    }

    @BeforeEach
    void createWebConfig() {
        final Map<String, Object> requestBody = new HashMap<>();
        requestBody.put("name", "test_webconfig");
        requestBody.put("urls", "http://www.example.com");
        requestBody.put("user_agent", "Mozilla/5.0");
        requestBody.put("num_of_thread", 5);
        requestBody.put("interval_time", 1000);
        requestBody.put("boost", 100.0);

Y **tus usuarios** definen de alguna manera (por ejemplo en un panel web en algún lugar) el **URL** donde tu aplicación debería enviar esas requests.

Toda la **lógica** sobre cómo registrar los URLs para webhooks y el código para realmente enviar esas requests depende de ti. Lo escribes como quieras en **tu propio código**.

## Documentando webhooks con **FastAPI** y OpenAPI

```console
$ OPENAPI_URL= uvicorn main:app

<span style="color: green;">INFO</span>:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
```

</div>

Então, se você acessar as URLs em `/openapi.json`, `/docs` ou `/redoc`, você receberá apenas um erro `404 Não Encontrado` como:

```JSON
{
    "detail": "Not Found"
}

You also define in some way at which **moments** your app will send those requests or events.

And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.

All the **logic** about how to register the URLs for webhooks and the code to actually send those requests is up to you. You write it however you want to in **your own code**.

- To be able to reliably use S3 multipart APIs feature of the SDKs without re-inventing the wheel of pre-signing the each URL in multipart API. This is very tedious to implement with all the scenarios of fault tolerance that's already implemented by the client SDK. The general client SDKs don't support multipart with presigned URLs.

        // Process multiple URLs
        String[] urls = { "http://example1.com", "http://example2.com", "http://example3.com" };

        for (String url : urls) {
            ResponseData responseData = new ResponseData();
            responseData.setUrl(url);

            ResultData resultData = transformer.transform(responseData);

     *     at java.net.URL.<init>(URL.java:480)
     *     at java.net.URL.<init>(URL.java:376)
     *     at java.net.URL.<init>(URL.java:330)
     *     at jcifs.smb.SmbFile.<init>(SmbFile.java:355)
     *     ...
     * </pre>
     *
     * </blockquote>
     *
     */
    public static void registerSmbURLHandler() {
        SingletonContext.getInstance();