All events are scoped by `subscriptionID`

[nvborisenko]

Usually we enable events via session.subscribe command with optional contexts/userContexts. On client side we are trying to associate the handler (method) which should be invoked as soon as client retrieved event from remote end. It becomes hard on client side to differentiate which event is directed whom.

It would be nice if event params contains subscription[], which indicates for whom this event should be dispatched. Like network interception: we see intercepters[] property.

[nvborisenko]

Trying to share simple use case to emphasize the issue:

        await bidi.Network.OnBeforeRequestSentAsync(e => Console.WriteLine("I came from ctx1"), new() { UserContexts = [ctx1] });

        await bidi.Network.OnBeforeRequestSentAsync(e => Console.WriteLine("I came from ctx2"), new() { UserContexts = [ctx2] });

Here I am subscribing to the event twice: for ctx1 and ctx2. Then later I want to execute different code based on what event came from. But technically I have no possibility to distinguish the events. I hope introducing subscriptions: [ +session.SubscriptionId ] can resolve this situation.