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 has been archived by the owner on Apr 22, 2023. It is now read-only.
I think that http.ServerResponse should emit a "end" (or something else) event to indicate that the response is done.
Why do I need this ?
Because I am in the case where I need to post files to the server. I would like to automatically remove uploaded files if not handled by the application.
That's why if there were a "end" event, I could remove files without being worried about if they are still needed by the application.
Generally, I think that is would be useful to know when the request is done.
The text was updated successfully, but these errors were encountered:
because it might disappear if it's not documented as public api. you can get around it by proxying the res.end() calls etc but this would be a lot less of a hack
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I think that http.ServerResponse should emit a "end" (or something else) event to indicate that the response is done.
Why do I need this ?
Because I am in the case where I need to post files to the server. I would like to automatically remove uploaded files if not handled by the application.
That's why if there were a "end" event, I could remove files without being worried about if they are still needed by the application.
Generally, I think that is would be useful to know when the request is done.
The text was updated successfully, but these errors were encountered: