The gem currently does not support the following use case.
1) A STOMP 1.2 client sends messages to a broker.
2) These messages have headers that require the encode / decode process.
3) A STOMP 1.0 client connects to the broker, and subscribes
4) The messages received will have encoded headers
We are assuming that the 1.0 client wants decoded headers.
The gem currently does not support the following use case.
1) A STOMP 1.2 client sends messages to a broker. 2) These messages have headers that require the encode / decode process. 3) A STOMP 1.0 client connects to the broker, and subscribes 4) The messages received will have encoded headers
We are assuming that the 1.0 client wants decoded headers.
Solution: always decode headers when received.