activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Commented: (AMQNET-205) Add support for Message Body Compression and Decompression
Date Tue, 10 Nov 2009 19:15:52 GMT


Jim Gomes commented on AMQNET-205:

Tim, I found the following on MSDN:

"The GZipStream class uses the gzip data format, which includes a cyclic redundancy check
value for detecting data corruption. The gzip data format uses the same compression algorithm
as the DeflateStream class."

What do you think about using GZipStream instead of DeflateStream class?


> Add support for Message Body Compression and Decompression
> ----------------------------------------------------------
>                 Key: AMQNET-205
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>    Affects Versions: 1.1.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.2.0
> Add the framework in NMS.ActiveMQ to deal with Messages that are tagged as Compressed,
as well as allowing messages to be sent with Compression.
> The Java based ActiveMQ client's ConnectionFactory allows a user to turn on Compression
for the Connections it creates, this causes the client to send messages with the message body
compressed using a Zlib compression algorithm.  The client can uncompress messages that it
receives that have the Openwire Compressed field set to true.  
> .Net doesn't have support for Zlib compression / decompression built in but there are
third-party libraries that can do this.  

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message