On 8/10/06, jhakim <[EMAIL PROTECTED]> wrote:
I can answer that - yes. .NET has extensive built-in support for compression.
Great - thanks. Do you fancy submitting some C# code to deal with compression? :) James
Hiram Chirino wrote: > > On 8/9/06, jhakim <[EMAIL PROTECTED]> wrote: >> >> Is compression of payload done only from publisher to JMS provider or all >> the >> way from publisher to JMS provider to consumer? >> > > publisher compresses and the consumer decompresses. Broker just moves > around a byte[] payload (he does not care if it's compressed or not). > >> If the answer is (as I would prefer it to be) that compression of message >> body is done all the way from publisher to client, then the follow up > > Yep. > >> question is whether or not compression is available (using NMS) if the >> publisher is a Java process and the consumer is a C# process. > > I don't think the C# client supports payload compression and > decompression yet. This is one of the reasons that compression is off > by default. Anybody know of .NET has gzip compression algorithms > included in the platform APIs? > >> -- >> View this message in context: >> http://www.nabble.com/Compression-from-provider-to-consumer-tf2081319.html#a5734124 >> Sent from the ActiveMQ - User forum at Nabble.com. >> >> > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > -- View this message in context: http://www.nabble.com/Compression-from-provider-to-consumer-tf2081319.html#a5745175 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
