Describe the bug

By design, connection pools create multiple connections and close them immediately if they are created on an RSS Core for which a connection was already created.

However, these transient connections are still sending notifications to the application on creation / connection / stop. This is problematic because it is very complex for an application to know which callbacks should be ignored and which callbacks correspond to an actual connection.

The connection pool should prevent notifications from the transient connection from reaching the app.

A potential fix would be to provide a temporary callback handler when creating the connection, and to switch to the app callback only once the connection is confirmed to be on a new RSS core.
The switch should likely be done from inside of a callback to limit concurrency issues.

Affected OS

• Windows
• Linux
• macOS
• Other (specify below)

Additional OS information

No response

MsQuic version

main

Steps taken to reproduce bug

Create a connection pool

Expected behavior

No spurious notifications

Actual outcome

Spurious notifications are received

Additional details

No response