factor out HTTP logic with ConnectStrategy abstraction #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been linked to Shortcut Story #133323: Break Python SSE client out of the SDK. |
keelerm84
approved these changes
Jan 4, 2023
# Conflicts: # ld_eventsource/__init__.py # ld_eventsource/actions.py # ld_eventsource/request_params.py # ld_eventsource/retry_delay_strategy.py # ld_eventsource/sse_client.py # testing/test_error_strategy.py # testing/test_retry_delay_strategy.py
# Conflicts: # ld_eventsource/__init__.py # ld_eventsource/config/__init__.py # ld_eventsource/request_params.py # ld_eventsource/sse_client.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the final set of API changes to make python-eventsource more closely resemble https://github.com/launchdarkly/okhttp-eventsource. The SSEClient class now has no knowledge of any HTTP implementation details; instead, it interacts with some implementation of
ConnectStrategy, where the default implementation contains all of the HTTP logic. This is a cleaner design and more flexible, and it allows us to write SSEClient unit tests that don't require real HTTP.