On 20/08/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > On Mon, 2007-08-20 at 10:42 +0100, Rupert Smith wrote: > > //Option3 - can use it with any message size, recomended for large > messages > > public void messageTransfer(String destination, short confirmMode, > > short acquireMode); > > public void headers(Struct... headers); > > public void data(byte[] data); > > public void data(ByteBuffer buf); > > public void data(String str); > > public void endData(); > > > > as if this is an important innovation. But then JMS has the > StreamMessage > > class, that provides this capability. > > Sorry but I must disagree with this statement as a JMS streamMessage is > just a convenient way of building a message that is eventually sent as > if. What you are describing would be equivalent to a JMS way of handling > large messages, that is to say splitting the message and sending small > batches to the broker. >
So is this what the example, 'Option3', is describing? Is it a streamed messages split into chunks? And we are doing streaming through the 'message class' now? I'm perfectly happy with that, but I see it as a JMS extensions, not replacement.
