Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support chunked transfer encoding #41

Closed
tanmaykm opened this issue Oct 8, 2021 · 0 comments · Fixed by #42
Closed

Support chunked transfer encoding #41

tanmaykm opened this issue Oct 8, 2021 · 0 comments · Fixed by #42

Comments

@tanmaykm
Copy link
Member

tanmaykm commented Oct 8, 2021

Some APIs may be designed to return a response with chunked transfer encoding. E.g. Kubernetes APIs that allow watches that return response that are chunked, with each chunk having one (? or more) response objects. There are ongoing discussions, but this is not something that follows a specified standard mechanism in Swagger/OpenApi yet, e.g. here and here.

Still, having a way to be able to call such APIs will be a big advantage.
@tanmaykm tanmaykm mentioned this issue Oct 8, 2021
Closed
tanmaykm added a commit that referenced this issue Oct 12, 2021
@tanmaykm
Support chunked transfer encoding
aaea97c 
Handle APIs that return chunked transfer encoded data. E.g. Kubernetes `watch` APIs.
Fixes #41
@tanmaykm tanmaykm mentioned this issue Oct 12, 2021
Merged
tanmaykm added a commit that referenced this issue Oct 12, 2021
@tanmaykm
Support chunked transfer encoding
bb07bcc 
Handle APIs that return chunked transfer encoded data. E.g. Kubernetes `watch` APIs.
Fixes #41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support chunked transfer encoding JuliaComputing/Swagger.jl
1 participant
@tanmaykm