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.

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

@SignalMethod threading configuration #214

Open
Tracked by #778
mfateev opened this issue Sep 18, 2020 · 0 comments
Open
Tracked by #778

@SignalMethod threading configuration #214

mfateev opened this issue Sep 18, 2020 · 0 comments
Labels
enhancement User experience

Comments

@mfateev
Copy link
Member

mfateev commented Sep 18, 2020

Is your feature request related to a problem? Please describe.
Each signal causes execution of a method annotated with @SignalMethod in its own thread. It means if the signal handling method blocks execution all other signals are still delivered through other threads.

In some scenarios the preferred semantic would be using a single thread to deliver all signals of the given type. This way workflow can flow control their processing. So while signal handling method is blocked all other signals are queued up waiting for thread to become available.

Describe the solution you'd like
Default signal handling to a single thread and provide an option through @SignalMethod parameter to multithreaded dispatch. Or do not provide multithreaded dispatch at all.

Describe alternatives you've considered
Keep it as it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement User experience
Projects
None yet
Development

No branches or pull requests

1 participant