-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event Subscriptions #23
Comments
Maybe this is not necessary. Developer need not to call SubscribeEvents, but can subscribe manually via SendCommand ("event plain xxxxxxxx") |
There's an experimental branch where this is implemented: |
Closed |
danbarua
added a commit
that referenced
this issue
Mar 4, 2016
danbarua
added a commit
that referenced
this issue
Mar 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently an
EventSocket
subscribes to a few events for convenience:In high-traffic/high-performance scenarios, users may wish to subscribe to only the minimum events.
Requirement: an
EventSocket
should subscribe to events lazily as and when they are required, for example, when I do anOriginate
it should, if necessary, subscribe to theBackgroundJob
andChannelExecuteComplete
events if not already done so.The text was updated successfully, but these errors were encountered: