Currently, the DeepL Java client Translator class utilizes its internal HttpClientWrapper, which is quite limited. Since it establishes a new connection for every request and lacks control over the task executor, it's suitable for infrequent usage. However, when sending a high volume of requests within a minute, resource constraints may become an issue. Is there a plan to enhance the client's capabilities?
Currently, the DeepL Java client Translator class utilizes its internal HttpClientWrapper, which is quite limited. Since it establishes a new connection for every request and lacks control over the task executor, it's suitable for infrequent usage. However, when sending a high volume of requests within a minute, resource constraints may become an issue. Is there a plan to enhance the client's capabilities?