Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Message Bus might send and listen to messages on different schedulers #47

Closed
haacked opened this issue Feb 10, 2012 · 3 comments
Closed

Message Bus might send and listen to messages on different schedulers #47

haacked opened this issue Feb 10, 2012 · 3 comments
Labels
outdated

Comments

@haacked
Copy link
Contributor

haacked commented Feb 10, 2012

The Listen method of MessageBus doesn't specify a scheduler. If you happen to call Listen for a type, and then send a message on a different scheduler than the default, it'll still get sent on the default scheduler because the Listen method creates a dictionary the first time and SendMessage calls the same dictionary.
haacked added a commit that referenced this issue Feb 11, 2012
@haacked
Add method to register scheduler per type and contract.
43258c2 
This resolves a bug in which listening for an event before sending the first message will lock all messages to the default scheduler rather than the one passed into the `SendMessage` method.
The API is now more explicit. Call `RegisterScheduler` to register a scheduler for each combination of message type and contract. If you don't register a scheduler, the default one is used. This ensures that `Listen` and `SendMessage` calls are always paired up properly on the same scheduler.
Closes Issue #47
@haacked
Copy link
Contributor Author

haacked commented Dec 18, 2013

Given this hasn't been updated for two years, I'll close it. 😄

@haacked haacked closed this as completed Dec 18, 2013
@anaisbetts
Copy link
Member

@haacked It's already fixed too, in that commit

@haacked
Copy link
Contributor Author

haacked commented Dec 18, 2013

Oh. Even better. ;) I must've forgotten to close it.

@lock lock bot added the outdated label Jun 26, 2019
@lock lock bot locked and limited conversation to collaborators Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
outdated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@anaisbetts @haacked