tibems_status tibemsBytesMsg_Create(tibemsBytesMsg* message );
message has usage pointer.
When your application creates a message, it also allocates storage for that message. This storage must subsequently be freed by a call to tibemsMsg_Destroy.tibems_status tibemsBytesMsg_GetBodyLength(tibemsMsg message,tibems_int* return_length );
message has usage pointer.
tibems_status tibemsBytesMsg_GetBytes(tibemsBytesMsg message,tibems_uint* byteSize );
message and bytes have usage pointer.
The function stores a pointer to the bytes of the message in this location.Your program must not change the bytes, which belong to the message; if you must modify the bytes, make a private copy first. tibems_status tibemsBytesMsg_ReadBoolean(tibemsBytesMsg message,tibems_bool* value );tibems_status tibemsBytesMsg_ReadByte(tibemsBytesMsg message,tibems_byte* value );tibems_status tibemsBytesMsg_ReadChar(tibemsBytesMsg message,tibems_wchar* value );tibems_status tibemsBytesMsg_ReadDouble(tibemsBytesMsg message,tibems_double* value );tibems_status tibemsBytesMsg_ReadFloat(tibemsBytesMsg message,tibems_float* value );tibems_status tibemsBytesMsg_ReadInt(tibemsBytesMsg message,tibems_int* value );tibems_status tibemsBytesMsg_ReadLong(tibemsBytesMsg message,tibems_long* value );tibems_status tibemsBytesMsg_ReadShort(tibemsBytesMsg message,tibems_short* value );tibems_status tibemsBytesMsg_ReadUnsignedByte(tibemsBytesMsg message,tibems_int* value );tibems_status tibemsBytesMsg_ReadUnsignedShort(tibemsBytesMsg message,tibems_int* value );tibems_status tibemsBytesMsg_ReadUTF(tibemsBytesMsg message,tibems_int* length );
message has usage pointer in all calls.value has usage pointer in tibemsBytesMsg_ReadUTF.
tibemsBytesMsg_ReadUTF reads a UTF-8 string. Since the length of the string cannot be determined in advance, the function stores the actual length in this location.The JMS specification defines eleven calls to extract data from the byte stream body of a tibemsBytesMsg.Each call reads a unit of data from the stream, and advances the read position so that the next read call gets the next datum.
Table 8 BytesMessage Read Functions tibemsBytesMsg_ReadShort tibemsBytesMsg_ReadUnsignedShort tibemsBytesMsg_ReadInt tibemsBytesMsg_ReadLong tibemsBytesMsg_ReadUTF tibems_status tibemsBytesMsg_ReadBytes(tibemsBytesMsg message,tibems_int requested_length,tibems_int* return_length );
message and value have usage pointer.
The program supplies a location. In that location, this call stores a pointer to the next block of bytes within the bytes message.Your program must not change the bytes, which belong to the message; if you must modify the bytes, make a private copy first. The function stores in this location the actual number of bytes that it read. (If the number of bytes remaining in the message is less than the requested_length, then this location indicates that number of remaining bytes. Your program must not use bytes beyond this limit.)When the function cannot read even one byte, it stores -1 in this location (and returns a successful status code).tibems_status tibemsBytesMsg_Reset(tibemsBytesMsg message );
message has usage pointer.
This call prepares a message body for reading, as if the message were newly received. Contrast tibemsMsg_ClearBody on page 26, which clears a message body in preparation for writing, as if it were newly created.tibems_status tibemsBytesMsg_SetBytes(tibemsBytesMsg message,tibems_uint byteSize );
message has usage pointer.
tibems_status tibemsBytesMsg_WriteBoolean(tibemsBytesMsg message,tibems_bool value );tibems_status tibemsBytesMsg_WriteByte(tibemsBytesMsg message,tibems_byte value );tibems_status tibemsBytesMsg_WriteChar(tibemsBytesMsg message,tibems_wchar value );tibems_status tibemsBytesMsg_WriteDouble(tibemsBytesMsg message,tibems_double value );tibems_status tibemsBytesMsg_WriteFloat(tibemsBytesMsg message,tibems_float value );tibems_status tibemsBytesMsg_WriteInt(tibemsBytesMsg message,tibems_int value );tibems_status tibemsBytesMsg_WriteLong(tibemsBytesMsg message,tibems_long value );tibems_status tibemsBytesMsg_WriteShort(tibemsBytesMsg message,tibems_short value );tibems_status tibemsBytesMsg_WriteUTF(tibemsBytesMsg message,
message has usage pointer in all calls.
The JMS specification defines these nine calls to insert data into the byte stream of a BytesMessage.Each call writes a data value to the stream, and advances the write position so that the next write call appends to the new end of the stream.
Table 9 BytesMessage Write Functions This function writes a 2-byte character—high byte first. For information about the UTF-8 format, see File System Safe UCS Transformation Format (FSS_UFT), X/Open Preliminary Specification, X/Open Company Ltd., Document Number: P316.This information also appears in ISO/IEC 10646, Annex P.tibems_status tibemsBytesMsg_WriteBytes(tibemsBytesMsg message,
message has usage pointer in all calls.
Copyright © TIBCO Software Inc. All Rights Reserved.