We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ExecutionContext has much too much functionality for a single class.
ExecutionContext
Needs to be split up into multiple classes.
File IO (directories, files, locks, buffers) only because of logging needs. Keep it with FileSystemAccessProvider.
Loggging using standard logging framework removes the need to centralize here.
On the other hand, keep global state, like BEJob states and executed jobs and commands here (for now).
Overall, clarify the exact purpose of RuntimeService, ExecutionContext, FileSystemAccessProvider, Configuration and
clean up all the mess!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ExecutionContext
has much too much functionality for a single class.Needs to be split up into multiple classes.
File IO (directories, files, locks, buffers) only because of logging needs. Keep it with FileSystemAccessProvider.
Loggging using standard logging framework removes the need to centralize here.
On the other hand, keep global state, like BEJob states and executed jobs and commands here (for now).
Overall, clarify the exact purpose of RuntimeService, ExecutionContext, FileSystemAccessProvider, Configuration and
clean up all the mess!
The text was updated successfully, but these errors were encountered: