[Messenger] Sanitize message when the receiver is another app

[nikophil]

Description

Hello,

Messenger is a great component, but has some drawbacks when it comes to send messages across different apps which use messenger.
Let's pretend an app A sends message through rabbitMQ, that will be consumed by an app B

Messages needs to be "sanitized" before leaving the app:

• stamps should be removed: if a stamp exists in app A and not in app B, when A sends messages to B, an error could occur. As well as if app A uses a bus which not exist in app B, B will try to get a bus which does not exist and an error will be thrown.
• header type could also be problematic: if PHP message objects in both apps do not have the same FQCN, when app B receives the message it will try to deserialize it in a class which does not exist.

A solution would be to add a new interface ExternalMessageInterface and take some actions when the interface is encountered in \Symfony\Component\Messenger\Transport\Serialization\Serializer.

I don't think we could fix this with a middleware, because the header type is added at serialization time.

I'd like to have some feedback on this before fixing it.

Thanks :)

[mdeboer]

For external applications you can use a custom serializer afaik. If so we could provide a simple JSON serializer that adds none of that stuff.

[lyrixx]

I also use plain JSON when dealing with interoperability. It's easier IMHO

[nikophil]

If so we could provide a simple JSON serializer that adds none of that stuff.

I agree with this: IMO this is such a common task, it should not require boilerplate code in user land, and maybe it should be documented

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Could I get an answer? If I do not hear anything I will assume this issue is resolved or abandoned. Please get back to me <3

[nesl247]

This has not been resolved.