-
Notifications
You must be signed in to change notification settings - Fork 6
feat: SSE #75
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
Conversation
| self.handleerror = handleerror | ||
| self.handlemessage = handlemessage | ||
|
|
||
| self.read_thread = threading.Thread( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does the threading here work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SSE Manager itself creates a thread managed by it - when a new url is found - it creates/updates the current thread used for processing the events incoming.
This is mostly required due to the eventsource client must run in its own thread - and you must read from the same thread that you started the client in.
No description provided.