Does the order of event handlers matter?

I'm writing a http connect forwarding proxy. And we have to handle the `connect` event.

This library associated a `connection` event that will eventually either destroy the socket, or handle a `close` event on the sockets.

Does it matter in what order the event handlers are added?

Furthermore if my event handler, is asynchronous, and awaits for various operations, such as establishing a connection to the target server, then it's possible that the socket created here is left dangling, or even the client socket is destroyed, while I attempt to write to it later.

How do I handle the problem where `stop` is run, while in the middle of an asynchronous request handler, do we just allow these exceptions to be thrown?

The issue names the connect, connection, close, and stop lifecycle events but no files or tests. Start by locating the event-handling and termination entry points, then trace how asynchronous handlers interact with socket cleanup. Done means the supported ordering and behavior during an in-flight request are clearly documented, including how callers should handle termination errors.

Written by the indexing model from the issue text.