Make MAX_STRING_NODE_LENGTH configurable #9995
Merged
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
Make MAX_STRING_NODE_LENGTH configurable
niloc132
reviewed
Aug 28, 2024
user/src/com/google/gwt/user/server/rpc/impl/ServerSerializationStreamWriter.java
Outdated
Show resolved
Hide resolved
niloc132
approved these changes
Aug 28, 2024
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.
Make
ServerSerializationStreamWriter.MAX_STRING_NODE_LENGTHconfigurable, to better work around #9578 and allow real JSON in all cases.This PR is a follow-up to #9961 (making the rpc serialization chunk size configurable).
Workaround #9578
Followup #9961