mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 08:47:12 +03:00
fe3419ff98
Summary: This is a bit of an abstract change, but the goal of this change is to make post-response handlers oblivious to the distinction between sending a response (or failing to send one) and returning a response that actually contains a (fallible) stream. The underlying / ultimate goal here is to move our error reporting out of ad-hoc router wrappers where we call `set_error_message` on some context entity, and to instead move it into post-response callbacks. The upshot of that is that if we fail to send a response even though we sent a 200 from the handler, we'll be able to log it! Indeed, remember that when sending a streaming response, we have to send a 200 to start streaming but we might hit an error producing later parts of the response! Reviewed By: mitrandir77 Differential Revision: D27966422 fbshipit-source-id: ab49639bfcc4af23ddc2e84181278f105ebb28b9 |
||
---|---|---|
.. | ||
src | ||
Cargo.toml |