-
Notifications
You must be signed in to change notification settings - Fork 583
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
Cache events listeners descend too far down the "firing sequence" for "unfireable events" #3169
Labels
Comments
chrisdennis
added a commit
to chrisdennis/ehcache3
that referenced
this issue
Jun 6, 2023
…lier event firing veto
chrisdennis
added a commit
to chrisdennis/ehcache3
that referenced
this issue
Jun 6, 2023
…lier event firing veto
Is there anything I can do to support resolving this issue? |
SamuelBussmann
added a commit
to SamuelBussmann/ehcache3
that referenced
this issue
Sep 26, 2023
Fixes ehcache#3169 : Track event listeners keyed by type to allow earlier event firing veto ehcache#3170
SamuelBussmann
added a commit
to SamuelBussmann/ehcache3
that referenced
this issue
Sep 26, 2023
…id submit delay
SamuelBussmann
added a commit
to SamuelBussmann/ehcache3
that referenced
this issue
Jul 18, 2024
Fixes ehcache#3169 : Track event listeners keyed by type to allow earlier event firing veto ehcache#3170
SamuelBussmann
added a commit
to SamuelBussmann/ehcache3
that referenced
this issue
Jul 18, 2024
…id submit delay
I've created an alternative/extended solution to this issue through Pull-Request #3236 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cache events listeners will get all the way to dispatching a task, including potentially spawning a thread , for events of a type for which there are no listeners. We have all the knowledge available to trim the call tree much sooner, and should be doing so.
The text was updated successfully, but these errors were encountered: