Incubating WebSocketNetworkTransport #5362
Closed
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.
Introduce a new
NetworkTransport
for WebSockets that rewrites most of the internal machinery:This fixes a couple of issues:
And should make debugging easier for other ones like:
The new
NetworkTransport
is namedWebSocketNetworkTransport
, just like the current one. The only thing that changes is the package name, fromcom.apollographql.apollo3.network.ws
tocom.apollographql.apollo3.network.websocket
. The current plan is to:apollo-websocket-network-transport-incubating
).WsProtocol
API that is wildly changed. Anyone using a customWsProtocol
will need to rewrite some code but I think this is for the greater good.Opening as draft the time to re-read everything and add KDoc
Relates to #5648