Copyright © TIBCO Software Inc. All Rights Reserved

> tibemsStreamMsg
> Type
> Purpose
> A message containing a stream of data items.
> Related Types
> tibemsMsg on page 21

> Member | Description | Page
> tibemsStreamMsg_Create | Create a stream message. | 110
> tibemsStreamMsg_FreeField | Free storage allocated during the reading of a stream message. | 111
> tibemsStreamMsg_Read | Read primitive datatypes from a stream message. | 112
> tibemsStreamMsg_ReadBytes | Read a byte array from a stream message. | 115
> tibemsStreamMsg_ReadField | Read a field from a stream message. | 116
> tibemsStreamMsg_Reset | Set the read position to the beginning of the stream, and mark the message body as read-only. | 117
> tibemsStreamMsg_Write | Write data to a stream message. | 118
> tibemsBytesMsg_WriteBytes | Write bytes from a byte array to a stream message. | 122

> Remarks
> Each datum in the stream must be a primitive type, or an object representation of a primitive type.
> Extensions
> TIBCO Enterprise Message Service extends the MapMessage and StreamMessage body types in two ways. These extensions allow TIBCO Enterprise Message Service to exchange messages with TIBCO Rendezvous and ActiveEnterprise formats that have certain features not available within the JMS specification.

> • | You can insert another MapMessage or StreamMessage instance as a submessage into a MapMessage or StreamMessage, generating a series of nested messages, instead of a flat message.

> • | You can use arrays as well as primitive types for the values.

> These extensions add considerable flexibility to the two body types. However, they are extensions and therefore not compliant with JMS specifications. Extended messages are tagged as extensions with the vendor property tag JMS_TIBCO_MSG_EXT.
> For more information on message compatibility with Rendezvous messages, see Message Body in TIBCO Enterprise Message Service User’s Guide.

Copyright © TIBCO Software Inc. All Rights Reserved