Multiple application subscribers on same machine not taking actions on notifications - #27
Open
jaredaz wants to merge 1 commit into
Open
Multiple application subscribers on same machine not taking actions on notifications#27jaredaz wants to merge 1 commit into
jaredaz wants to merge 1 commit into
Conversation
…that don't share local cache were ignoring update and delete subscriber actions.
Contributor
|
Thanks, I'll look into it! |
Author
|
Cool, let me know if I can help or if you want changes to my PR :-). |
Author
|
Any updates on this PR? I would love to be able to go back to using the published nuget package :-). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ran into an issue on our web servers that run many applications that are both publisher and subscribers. For instance, our API updates the cache and the Web application is a subscriber to the events, but ignores them because it's on the same machine. This will overcome that without removing the optimization of not performing updates and deletes on the publishing application.