[ISSUE #3526] Optimize SubStreamHandler #3527
Conversation
|
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
| @Slf4j | ||
| public abstract class ThreadWrapper implements Runnable { | ||
|
|
||
| private final AtomicBoolean started = new AtomicBoolean(false); | ||
| protected Thread thread; |
There was a problem hiding this comment.
Besides its usage in SubStreamHandler, could ThreadWrapper be utilized in other classes as well?
ThreadWrapper appears to streamline synchronization for SubStreamHandler, eliminating the need for using a latch. However, the synchronization mechanism using latch in SubStreamHandler itself isn't overly complex. Hence, I'm curious whether introducing the additional complexity of ThreadWrapper for synchronization would address additional problems.
|
It has been 60 days since the last activity on this pull request. I am reaching out here to gently remind you that the Apache EventMesh community values every pull request, and please feel free to get in touch with the reviewers at any time. They are available to assist you in advancing the progress of your pull request and offering the latest feedback. If you encounter any challenges during development, seeking support within the community is encouraged. We sincerely appreciate your contributions to Apache EventMesh. |
Fixes #3526
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Optimize SubStreamHandler
Documentation