Replace Server Interactivity with WebAssembly #1
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
martijn
force-pushed
the
move-to-webassembly
branch
from
2e4de09 to
8166ea2
Compare
Drop ReadyToRun for now since I can't seem to get this to skip the client project
martijn
changed the title
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.
Blazor InteractiveServer render mode proved to be unpractical for mobile users especially. Rearchitected the project to use InteractiveWebAssembly mode for the Game page. The client-side GameContext uses a SignalR connection to the backend.
This also removes MassTransit as a messaging backend. Let's worry about scaling beyond a single worker process later.