Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=UhmzWiCNjcZjNn2iAYDIMZsBXvMChwFe2rf7M9A2acjSGnjuYAiwz8TPcYXtHjvHqtsLKebYqEiJ18jVVvLyU87ui92ftu9u9M+FGYvPp/qMiaJL3Eef60wDSfxzN/cCuny559XRAvrqPXJXVWpcPs4gicUAYVG0WDYhHO+r/Ns=
Message-ID: <ec6e67fd0610061049g1359da33vbc08e250f214f81@mail.gmail.com>
Date: Fri, 6 Oct 2006 18:49:29 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Using ActiveMQ from .NET compact framework
In-Reply-To: <h5hiv3-55k.ln1@td.selfip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <opphv3-55k.ln1@td.selfip.net>
	 <af2843cd0610060947w23ba6275w728db7e916534213@mail.gmail.com>
	 <h5hiv3-55k.ln1@td.selfip.net>

On 10/6/06, Oleg Deribas <thisaddressisnotmine@td.selfip.net> wrote:
> Hello,
>
> Hiram Chirino said the following on 06.10.2006 19:47:
>
> > I don't see why it would not work.. Why don't you setup it up and let us
> > know how it goes.
>
> I've tried it. I've created two additional projects (attached) for the
> solution. NMS project building is fine, but there are small problems
> with activemq project - it uses Monitor.PulseAll and Monitor.Wait
> methods not supported by compact framework. I'll try to investigate if
> it is possible to avoid these methods usage.

I wonder if there's an alternative way of doing these kinds of
monitors / semaphores in .Net? BTW does .Net compact framework support
threads?


> >> And I have another question - how much traffic required for one simple
> >> message (like event notification)? I will use GPRS connection from PDA,
> >> so traffic is not cheap...
> >
> > We use lots of tricks in openwire to keep the message sizes as small as
> > possible but that does not deal with the message content compression.
>
> I mean just what overhead of wrapping data into messages. For example,
> for empty message - what is the smallest possible message size?

Its probably simplest to send an empty message and see how many bytes it uses :)


> > And I think payload compression is still a feature that has not yet been
> > implemented in the .NET client implementation.
>
> But payload compression is the part of protocol specification?

Yes - using GZip

> Anyway compression could be implemented on the application level.

Sure - though its easy to support in openwire

-- 

James
-------
http://radio.weblogs.com/0112098/