Skip to content

Too strict condition to close the connection #37

@nomo-nvm

Description

@nomo-nvm

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions