The protocols involve much more than just the message itself, and the protocols are completely different between 1.0 and 0-x (indeed even 0-10 and 0-9[-1] were rather different from each other too), with the messages themselves then pretty different on top, which is why its not typical for clients (or many brokers) to supports both 1.0 and any 0-x. So it is not simply a case of just converting the message, but a case of implementing each full different protocol to talk to the producers/consumers connections and also making some decisions on what/how different message bits will convert as messages are sent/received across them. Is it possible, yes to an extent...that is what the broker has supported so far and is specifically what this thread is about eventually removing, given it is a significant burden to maintaining and updating the broker (especially in the context that the projects main focus has been on 1.0 clients for well over a decade now and that we no longer have any 0-x clients).
Without the broker doing such multi-protocol stuff itself you would more typically be bridging between two different systems (e.g with an intermediate component talking to both and doing application-specific conversion between them) whilst the end applications are updated to use the new one and the older system can then be shut down. On Tue, 22 Sept 2026 at 13:57, Claude Warren <[email protected]> wrote: > > > I am very late to this discussion. > > I have a requirement for a customer to read older versions as they transition > from older to newer versions. > > I don't know enough about the underlying protocol to know if it would be > possible to build a layer that would translate say a 0.9 message into a 1.0 > and be able to handle the communication to the 0.9 producer. Is this so > complex that it needs the full broker? Is there some way to create a way to > make it easy to migrate from earlier protocols? > > Currently it looks like using a Broker is the only way to do this. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
