activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <>
Subject Re: Stomp and Message Types
Date Mon, 24 Apr 2006 02:17:14 GMT
How about we make that an optional extensible header that defaults to
"binary" if not set.  All stomp implementations should at least
support text and binary.   Something like:


And activemq would also support some other types such as:
activemq-map, activemq-stream, and activemq-object where ActiveMQ
would define the expected body encoding for those types.


On 4/23/06, Brian McCallister <> wrote:
> 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


View raw message