Include separate types for handshaked and non-handshaked connections

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • 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.

              Assignee:
              Patrick Freed
              Reporter:
              Patrick Freed
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: