Is NServiceBus 2.0 allowed to define the serializer for the given message type?
I want to all but one of my messages has to be serialized using the XmlSerializer, the remaining one should be serialized using binary surrelease.
Is it possible with NServiceBus 2.0?
I believe that the serial is specified on a closing point, hence the use of all the end points All the messages having to be done will be to use the same serializer.
However, if you recommend a message type per-end point / line queue nssbees, you can effectively distinguish one message type and use
< P> Edit in response to the comment
Indirectly under routing with the distributor It has been mentioned. Udi combustion also often advises this, although this link is difficult to provide because the search is not bad.
Actually, the idea is that you have high priority messages with less priority, and that if you need to, then you can get the most flexibility to measure fixed message processing.
Because MsmqTransportConfig only allows to specify an input queue, having a queue per message type means that you have only one message handler per endpoint.
To address the image, if you encode the byte array as a base-64-encoded string, you can still interpret it in an XML-formatted message. This is not ideal, but if your images are not very large, then it may be easier by simply going through the hassle of using a different serializer on a message type.
Another option is to store data or out-of-band data in the data system, and then see it by ID or path (gradually).
Comments
Post a Comment