clarify comments around cancellation cases (#84)

amqp · Apr 15, 2021 · 8873a97 · 8873a97
1 parent 7f7a08b
commit 8873a97
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/lib/connection.ts b/lib/connection.ts
@@ -549,7 +549,7 @@ export class Connection extends Entity {
  // our `onOpen` handler should have executed and removed this abort listener.
  // This is a 'just in case' check in case the operation was cancelled sometime
  // between when the session's state was updated and when the sessionOpen
- // event was emitted.
+ // event was handled.
  rheaSession.close();
  } else if (!rheaSession.is_closed()) {
  // If the rheaSession isn't closed, then it's possible the peer will still

diff --git a/lib/session.ts b/lib/session.ts
@@ -291,7 +291,7 @@ export class Session extends Entity {
  // our `onOpen` handler should have executed and removed this abort listener.
  // This is a 'just in case' check in case the operation was cancelled sometime
  // between when the receiver's state was updated and when the receiverOpen
- // event was emitted.
+ // event was handled.
  rheaReceiver.close();
  } else if (!rheaReceiver.is_closed()) {
  // If the rheaReceiver isn't closed, then it's possible the peer will still
@@ -464,7 +464,7 @@ export class Session extends Entity {
  // our `onOpen` handler should have executed and removed this abort listener.
  // This is a 'just in case' check in case the operation was cancelled sometime
  // between when the sender's state was updated and when the senderOpen
- // event was emitted.
+ // event was handled.
  rheaSender.close();
  } else if (!rheaSender.is_closed()) {
  // If the rheaSender isn't closed, then it's possible the peer will still