### Resource Cleanup Pattern

Always use try-with-resources for `ResponseData` - temp files are auto-deleted on close.

## Log Message Guidelines

- Format parameters as `key=value` (e.g., `sessionId={}`, `url={}`)
- Prefix with `[name]` when context identification is needed
- Use full words, not abbreviations

Given the simplicity of Flask, it seemed like a good match for building APIs. The next thing to find was a "Django REST Framework" for Flask.

/// check | Inspired **FastAPI** to

Be a micro-framework. Making it easy to mix and match the tools and parts needed.

Have a simple and easy to use routing system.

///

        // Test that deleting already deleted file doesn't throw
        Path tempFile = Files.createTempFile("already_deleted", ".tmp");
        Files.delete(tempFile);
        assertFalse(Files.exists(tempFile));

        // Should return false without throwing
        boolean deleted = Files.deleteIfExists(tempFile);
        assertFalse(deleted);
    }

    @Test

    // Test execute with successful purge (single file deleted)
    @Test
    public void test_execute_singleFileDeleted() {
        thumbnailManager.setPurgeCallCount(1);

        String result = purgeThumbnailJob.execute();

        assertEquals("Deleted 1 thumbnail files.", result);
    }

    // Test execute with successful purge (multiple files deleted)
    @Test
    public void test_execute_multipleFilesDeleted() {

        assertEquals(8, testClient.deletedIndices.size());
        // Verify original index names appear in deleted list (old index deletion at step 3)
        boolean foundOriginalDelete = false;
        for (final String deleted : testClient.deletedIndices) {
            if (!deleted.contains(".backup.") && !deleted.contains(".rebuild.")) {
                foundOriginalDelete = true;
                break;
            }
        }

        refresh();

        // Verify all old sessions are deleted (size should be 0 after deletion)
        final List<Map<String, Object>> logListAfter = readCrawlingInfo(webConfigId);
        logger.info("logListAfter: {}", logListAfter);
        assertEquals(0, logListAfter.size(), "All crawling info logs should be deleted after calling delete all endpoint");

        // Log the result

        assertEquals(6, MoreFiles.listFiles(dir).size());

        method.delete(dir);
        method.assertDeleteSucceeded(dir);

        assertEquals(
            "contents of /dontdelete deleted by delete method " + method,
            3,
            MoreFiles.listFiles(fs.getPath("/dontdelete")).size());
      }
    }
  }

  public void testDirectoryDeletion_emptyDir() throws IOException {

success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.
success.job_started = Started a job: {0}.

success.crawling_info_delete_all = Deleted session data.
success.start_crawl_process = Started a crawl process.
success.upload_design_file = Updated {0}.
success.update_design_jsp_file = Updated {0}.
success.create_crawling_config_at_wizard = Created a crawling config {0}.
success.failure_url_delete_all = Deleted failure URLs.
success.delete_file = Deleted {0} file.
success.job_started = Started a job: {0}.

setting [Transport.DisableKeepAlives] to `true` will disable connection reuse.
However, such performance degradation usually indicates improper configuration
or usage of [Transport] or [Client] in the first place, and a deeper look would