-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
We currently use a single Connection type throughout the driver, both in pre-handshake and post-handshake scenarios. This requires us to wrap the StreamDescription stored on a Connection in a Result, since it may not be present if the handshake fails. We should model this differently so that connections used post-handshake don't have to handle the possibility of an error when accessing the StreamDescription.
- related to
-
RUST-1454 Use separate types for pooled and non-pooled connections
- Closed