Skip to content

CustomOnionMessageHandler::handle_message doesn't expose the reply_path #2882

Description

@TheBlueMatt

I'm trying to implement an onion message handler that does some work async and then eventually replies to an onion message. However, handle_message currently only exposes the message itself but not the reply path, which would be needed to be able to respond async. To avoid cloneing the BlindedPath in such a case, maybe it makes sense to drop the whole reply-inline logic and force users to reply via release_pending_custom_messages?

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