Description

Apologies if this has already been discussed. I searched open and closed issues and PRs and wasn't able to find anything relevant.

ListableReceiverInterface requires defining two additional methods, all() and find() methods for a transport receiver to be "listable". My understanding is that Messenger is using Redis Streams to implement "queues" for messages, for which Redis provides XREAD and XRANGE commands for accessing items in the stream or to find a specific item by id, so I'm wondering whether it should be possible to make RedisReceiver implement ListableReceiverInterface or if there are some other restrictions that prevents this. This would help with tools like zenstruck/messenger-monitor-bundle, which are presently unable to show queued messages from Redis-backed transports.

Example

No response