Support streaming JSON formats such as json-seq#3735
Closed
handrews wants to merge 1 commit intoOAI:v3.2.0-devfrom
Closed
Support streaming JSON formats such as json-seq#3735handrews wants to merge 1 commit intoOAI:v3.2.0-devfrom
handrews wants to merge 1 commit intoOAI:v3.2.0-devfrom
Conversation
These formats can easily be modeled as if they were JSON arrays, with fairly minimal new tooling requirements.
handrews
added
enhancement
media and encoding
ralfhandl
approved these changes
Apr 26, 2024
Member
Author
|
Moving to draft for now as 3.2 PRs that aren't ports from the patch releases can wait until after we finish the patch releases. |
miqui
approved these changes
May 9, 2024
Member
Author
|
Closing this in preparation to re-submit once the repo is re-organized for 3.2 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These formats can easily be modeled as if they were JSON arrays, with fairly minimal new tooling requirements. As documented in the linked issue, there is ample evidence for their use, and the different formats do not require different modeling approaches. This approach works for all known current streaming formats (which may or may not be literally streamed in the HTTP sense).
This seems like a nice, small-but-impactful enhancement for 3.2.0.