Closed kyri-petrou closed 1 month ago
/bounty $250 but has to ship soon because of final release coming up.
/attempt #2908
with your implementation plan/claim #2908
in the PR body to claim the bountyThank you for contributing to zio/zio-http!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🔴 @abhi267266 | Aug 3, 2024, 9:26:19 AM | WIP |
🟢 @Ahmadkhan02 | Aug 4, 2024, 8:48:55 PM | #3003 |
/attempt #2908
/attempt #2908
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@Ahmadkhan02 | 1 bounty from 1 project | TypeScript, Jupyter Notebook |
Cancel attempt |
[!NOTE] The user @abhi267266 is already attempting to complete issue #2908 and claim the bounty. We recommend checking in on @abhi267266's progress, and potentially collaborating, before starting a new solution.
💡 @Ahmadkhan02 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
🎉🎈 @Ahmadkhan02 has been awarded $250! 🎈🎊
Is your feature request related to a problem? Please describe. Currently,
zio-http
provides 2 config options forRequestStreaming
:Disabled
(with a maximum number of bytes that the request can be before rejecting it)Enabled
(requests are streamed regardless of size)For servers with low latency / high performance requirements, disabling streaming is a favourable option as it's more performant than streaming the requests. However, in some cases we might want to be able to be able to handle very large requests, so it would be good if
zio-http
provided an option to aggregate the response if it's less than X bytes, and stream it if it's larger than thatDescribe the solution you'd like Another case class extending
RequestStreaming
similar toDisabled
but instead of failing the request it streams the bytes insteadDescribe alternatives you've considered Enabling streaming and using a middleware to batch the
ZStream
, but this doesn't perform as well as I would have hoped