pardahlman
commented
8 years ago @mrfamazing sorry for not decorating this ticket with description. This ticket is in fact more of a note-to-self; I want to make sure to dispose internal resources (MessageContext caches for message chaining).
However, making RawRabbit compatible with clients from other libraries and languages should not be a problem. After all, messages are serialized to json by default and headers are provided as expected :+1: . The framework itself is very modular, and it is pretty straight forward to register your own implementation of say IMessageContextProvider or IBasicPropertiesProvider etc. From the top of my head there are two things that might need to be tweaked:
- The base class for the message context provider,
MessageContextProviderBase, and particular the methodExtractContextassumes that the header is not null. A null check that bailes out with a newTMessageContext, should be enough to get the message to the handler. - Perhapes make adjustment to the registered
JsonSerializer. Json.Net is configured to serialize$typeinformation, which clients that uses other message serialisers than Json.Net might not like.
I'm currently working with support for .NET Core #99 #102, but as soon as I'm done I'll look closer at this. Let me know if you're making any progress!
mrfamazing
Is the goal here to make RawRabbit more open to messages from any publisher/subscriber, not just .net/RR? I am trying to use RR with a system has other clients that might pub/sub. Message context is one of the things that I am running into trying to send a message from another system. It's a little more complex then just adding a new serializer to consume messages from elsewhere, if impossible at this time. If this isn't the goal of RawRabbit, then you can disregard this, otherwise that would be a great path to go down.