Object messages are used for objects created in .NET or Java. A C program can create, receive, and send object messages. For example, a C application can forward or store an object generated from a Java or .NET application.
C programs cannot create object messages. However, a C program can receive an object message from a Java or .NET program, and forward it, or store it for later resending.
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.
When the message does not contain an object (because none has been set), this function places null in the
bytes argument, and zero in the
byteSize argument.
Setting the content of an object message stores a snapshot of the object. subsequent changes to the original object or its serialized representation (as a byte sequence) do not affect the message.