Open topic with navigation

TIBCO Rendezvous® 8.8.0

# Avoid Sending Binary Data Buffers or Internal Structs

Rendezvous programs can exchange binary data buffers using datatype TIBRVMSG_OPAQUE. The program is free to use any format and content within opaque data. However, it is good practice to avoid extensive use of opaque data.

For example, opaque buffers can contain data structures mapped by C language structs—but beware, this technique couples your programs rather tightly to the data structure. If you change the struct definition in the sender, you must also change it in the listener, and vice versa. Exchanging structs also makes it more difficult to introduce new, interoperating programs in the future. Furthermore, exchanging internal structs makes it difficult to for your program to interoperate with programs developed in other languages.

Binary data and internal structs are also platform dependent—you cannot exchange raw, binary data between programs running on machines that represent numbers or character strings with different formats.

Instead of binary buffers or structs, consider using Rendezvous self-describing data to ease data exchange. Rendezvous datatypes span the most common atomic and array datatypes of most programming languages, and Rendezvous messages can emulate any struct or composite datatype.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2025. Cloud Software Group, Inc. All Rights Reserved.