After thinking all of this through, we've decided to use RFH2 in a pilot application. It seems to be exactly what we need. The application team was starting to design a solution that Mime-encoded the binary data, but RFH2 makes much more sense.
| marty <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]> 10/05/2004 07:34 PM
|
|
FWIW, I've found an MQRFH2 header a useful place to store metadata while
the payload can be binary. Since the name/value info is user-defined,
extensible, and converted by a qmgr as necessary it could be of use in
this scenario. i.e. it can be of great use when you wish to send
textual meta-data and binary data in the same message.
We've used MQRFH2 headers with much success in transporting compressed
file data as messages. We send all sorts of metadata about the file
along with the binary payload - it's original name, file type, source
system, length, requested destination, digest info, etc. The receiving
app uses the metadata to help it verify content and write the file to
it's destination.
HTH, and as always YMMV :-)
marty
Scott Gray wrote:
> If you combine binary and text data in a single message you may have
> to write your own data conversion exit if you plan to cross platforms.
> Scott
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
