-
Notifications
You must be signed in to change notification settings - Fork 111
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.
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
Support Streaming #79
Comments
Definitely interested in this. |
@conico974 were you able to cache the streamed data? I tried playing w/ streaming in server-adapter but the content type ended up being an |
Yes it was kind of working, i hacked something here : https://github.com/conico974/open-next/blob/688150d0a09d78a12f0ba926097c8282b6ec2745/packages/open-next/src/adapters/response.ts#L85 to set the content type. There is also a |
@conico974 I've forked your commit and investigating further. Found this function sets content type after the stream has already been written to. |
@DavidHooper Nice catch looking at the runtime. |
Is there any update on this? I would love to see it implemented! |
@passgoco https://discord.com/channels/983865673656705025/1027265626085019769/1149742408565800990 |
AWS Lambda just introduced streaming capabilities via Lambda URLs. Opening this issue to gather some thoughts/interests from the community.
Ref:
https://beta.nextjs.org/docs/data-fetching/streaming-and-suspense
https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/
The text was updated successfully, but these errors were encountered: