Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com
 designates 72.14.246.249 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Clzc55pr+bIUcMthrWLJOAp/xrMu0leqrJHatwVAflvKs3jKEMbL/GZjkCDGIzfdexz+k7QgSYVg/mnxH40IB1ezzBf2xmI/PXUJpuixyVD93bbhqIaw5JyKDHtoAOWj1kUVjko5IOM0b61RoQ47QKztQ++yrPLa9b67WLxm3ag=
Message-ID: <ec6e67fd0703290049h2dfb2685u44a427691a4de5ee@mail.gmail.com>
Date: Thu, 29 Mar 2007 08:49:13 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: DESIGN GUIDANCE PLEASE: Initial Set of Messages followed by
 Incremental Messages
In-Reply-To: <9722255.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9722255.post@talk.nabble.com>

This sounds like request-response; the only difference is after the
clients initial request, there are multiple responses over time
(initial ones then incremental ones)...

http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html

namely clients have their own temporary queue.

If the incremental responses are actually common to many clients (e.g.
you are sending out price changes as deltas, but each client needs to
know the current initial data first before they can understand the
deltas) then you can use a topic for the responses and use a custom
hook in the subscription recovery policy...

See QueryBasedSubscriptionRecoveryPolicy
http://activemq.apache.org/subscription-recovery-policy.html
http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/region/policy/QueryBasedSubscriptionRecoveryPolicy.html

where you supply your own MessageQuery to provide a clients initial
set of messages...
http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/region/policy/MessageQuery.html


On 3/28/07, sparky2708 <daa82@columbia.edu> wrote:
>
> Hi,
>    I am looking for suggestions/example code on how to do the following:
>
> (1) On client startup my service would Initially push out some messages to
> the client
> (2) Push out incremental messages to client when responding to some other
> message that I receive
>
> So for (1) I was thinking I would need the client to send a message
> indicating a request for the initial state. I was thinking that at that
> point I would create some queue and tell the client to subscribe to messages
> in that queue (I would have to make that queue unique somehow. Any ideas?).
> The client would subscribe to the incremental updates at that point so no
> incremental messages are missed. I would then push out the intitial messages
> and then the incremental ones.
>
> Is there an easy way to do this? Are there any examples of how I can do
> this?
> --
> View this message in context: http://www.nabble.com/DESIGN-GUIDANCE-PLEASE%3A-Initial-Set-of-Messages-followed-by-Incremental-Messages-tf3482857s2354.html#a9722255
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

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