Resolution:
Environment:
==========
All

Resolution:
========

1). Compression and decompression of the message is done at the client level by the EMS client library. C clients use the ZLIB compression library. Java clients use the java.util.zip.Inflater/Deflater (which is based on ZLIB).  We use the default compression level.  

Message compression is supported in .NET clients when using the install package for Visual C++ 8 / .NET 2.0. The .NET 2.0 client library EMS uses is the built in compression with .NET 2.0. .NET in the Visual C++ 7 / .NET 1.1 package does not support compression.

2). TIBCO Enterprise Message Service allows a client to compress the body of a message before sending the message to the server.  To set message compression, the application that sends or publishes the message must access the message properties and set the boolean property JMS_TIBCO_COMPRESS to “true” before publishing the message.

Example:

message.setBooleanProperty("JMS_TIBCO_COMPRESS",true);

Compressed messages are handled transparently by the EMS client library. The client code only sets the JMS_TIBCO_COMPRESS property.  The client does not need to take any other action.  Receiving clients of compressed messages will decompress the messages automatically.

Is compression and decompression done on the client side by the EMS client libraries or is it done by the EMS server?