I want to correct a design wart in ActiveMQ's Stomp implementation -- originally Stomp only supported text and I implemented messages as text messages. Later I caved and changed stomp to handle arbitrary byte bodies, and used byte messages to handle this.

The difference, according to ActiveMQ, is whether the content-length header is specified (if it is not, it goes into text mode and scans for a null byte).

I'd like to change activemq to *always* use byte messages.

-Brian

Reply via email to