Feature Request: Configurable Client Timeouts #1021
Description
Summary
We'd like a way for Smithy-generated Java clients to have configurable timeouts (e.g., connection timeout, read timeout, socket timeout, etc.). Based on conversations with the Smithy team, this setting is not currently exposed to end users, but having the ability to configure these values is critical for building resilient and performant applications.
Motivation / Use Case
- Varying network conditions: Different deployment environments (cloud, on-premises, edge) have different latency characteristics and require tailored timeout configurations.
- Failure handling: Without configurable timeouts, clients may hang indefinitely on unresponsive services, leading to resource exhaustion and cascading failures.
- SLA compliance: Our applications have strict latency requirements, and we need the ability to fail fast when downstream services don't respond within acceptable thresholds.
- Retry strategies: Proper timeout configuration is essential for implementing effective retry and circuit-breaker patterns.
Desired Behavior
We would like the ability to configure (at minimum):
- Connection timeout: Maximum time to establish a connection
- Read timeout: Maximum time to wait for data after a connection is established