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 Sep 13, 2018. It is now read-only.
Currently, the out body is polled right after receiving a Frame::Message. This may be desirable in some instances, but it may also be undesirable. One example of wanting to disable it is to enable 100-continue expectations in HTTP/1.
It's been noticed in the gitter channel that to do this, either mpsc would need to grow the functionality to check if a user has ever polled on the Receiver, or Body could also change from using mpsc to a custom channel with the functionality added.
The text was updated successfully, but these errors were encountered:
Currently, the out body is polled right after receiving a
Frame::Message
. This may be desirable in some instances, but it may also be undesirable. One example of wanting to disable it is to enable 100-continue expectations in HTTP/1.It's been noticed in the gitter channel that to do this, either mpsc would need to grow the functionality to check if a user has ever polled on the
Receiver
, orBody
could also change from usingmpsc
to a custom channel with the functionality added.The text was updated successfully, but these errors were encountered: