User Experience

• Currently, if a user calls client.connect() and client.close() concurrently, it would leave the client in an indeterminate state

Risks/Unknowns

• What is the desired behavior?
  • Proposed Plan 1:
    • when connect() is called during close(), await close()
    • when connect() is called during close(), await connect()
    • potential problems:
      • this could create a confusing user experience in the event that a connectionCheckedOutEvent and connectionClosedEvent are both emitted through a call to client.close()
      • it also creates more resources for client.close() to clean-up
  • Proposed Plan 2:
    • when connect() is called during close(), throw an runtime / API error 
    • when close() is called during connect(), abort connect()  (should be handled by NODE-6632)
    • potential problems: 

Acceptance Criteria

Implementation Requirements

• Determine and implement desired behavior

Testing Requirements

• TBD

Documentation Requirements

• TBD