Hi,
It seems should_shut_down() is a little bit to strict. For the future to gracefully exit, the application needs both producer (the handle, _ in example) and consumer (messages) to be dropped (see here). However in an application when the receiver is moved to a new task, there is no way to drop it.
How to gracefully exit the connection future?
edit: if the should_shut_down() would check whether the requests_rx is closed (and only this), my app could just drop the handle and be done with it.
Hi,
It seems should_shut_down() is a little bit to strict. For the future to gracefully exit, the application needs both producer (the handle,
_in example) and consumer (messages) to be dropped (see here). However in an application when the receiver is moved to a new task, there is no way to drop it.How to gracefully exit the connection future?
edit: if the
should_shut_down()would check whether therequests_rxis closed (and only this), my app could just drop the handle and be done with it.