Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com
 designates 66.249.92.168 as permitted sender)
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=r9EmwANtv6d7QcKNim3QMAKfN3Ips7GY6Dwuxx7MQmW0eKmnmWgL6uD4uMjd+Z7LWez1N9Bv1OYWEmpOkYdMK1WSHs08z00xNqtwpvqitDFXqmPX1i2TA0Sfkd1kOqYwAoMpKAqQIqTUL1rtAqAH346BkR88LrHq2Mpqd8DSCzQ=
Message-ID: <ec6e67fd0604190103t711964bh8cf05137d3d11cc5@mail.gmail.com>
Date: Wed, 19 Apr 2006 09:03:25 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: ActiveMQ and Ajax
In-Reply-To: <3983116.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <3964102.post@talk.nabble.com>
	 <ec6e67fd0604181043k1585d40ey5f32ff66d5928a17@mail.gmail.com>
	 <3974657.post@talk.nabble.com>
	 <ec6e67fd0604181418y28d55564m727e14f4bb575d7a@mail.gmail.com>
	 <3981852.post@talk.nabble.com>
	 <ec6e67fd0604190017p26fe7faeh21957af8f4774e7@mail.gmail.com>
	 <3983116.post@talk.nabble.com>

On 4/19/06, ssozonoff <serge@sozonoff.com> wrote:
>
> Thanks I will give this whole issue some more thought.
>
> BTW with regards to Comet, my understanding is that it is truely push bas=
ed
> and does not require more than a single poll to get started after which
> events are pushed. In that case I guess your Ajax solution would be a sor=
t
> of hybrid since there is a poll every 20-30 seconds.... and I still agree
> that it would be more robust.

Yeah - Comet is as good as you can get over HTTP. With C#/Java
clients, we can stream lots of messages (say 1000 of them) to the
client asynchronously so they get unmarshalled into Message objects in
the background, so the consumer doesn't have to wait for each message
to arrive; leading to real high performance.


> Another alternative would be to use XMPP and JEP 124 to get it over HTTP =
but
> this does not address the Push aspect... only the transport layer. I saw
> somewhere that there was some XMPP support in ActiveMQ.

Yeah- but its Java only though - you'd need a C# client.

--

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