You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 24, 2022. It is now read-only.
Hi I'm not sure if this is supported or not, but as far as I can tell this middleware doesn't support (memory) efficient serialisation of large responses.
From looking at the code it seems that objects are fully converted into in memory strings before being returned to the web server. Is this a fair assessment?
Would it be possible to support streaming responses with this middleware?
Perhaps by allowing certain handlers to return a piped-input-stream instead of a String?
The text was updated successfully, but these errors were encountered:
Hi I'm not sure if this is supported or not, but as far as I can tell this middleware doesn't support (memory) efficient serialisation of large responses.
From looking at the code it seems that objects are fully converted into in memory strings before being returned to the web server. Is this a fair assessment?
Would it be possible to support streaming responses with this middleware?
Perhaps by allowing certain handlers to return a piped-input-stream instead of a String?
The text was updated successfully, but these errors were encountered: