Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6D5DD200CEB for ; Sat, 12 Aug 2017 23:05:40 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6BC25164A9F; Sat, 12 Aug 2017 21:05:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B1A6A164A9E for ; Sat, 12 Aug 2017 23:05:39 +0200 (CEST) Received: (qmail 51954 invoked by uid 500); 12 Aug 2017 21:05:37 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 51943 invoked by uid 99); 12 Aug 2017 21:05:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Aug 2017 21:05:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 092B718073A for ; Sat, 12 Aug 2017 21:05:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.979 X-Spam-Level: * X-Spam-Status: No, score=1.979 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 5NVcYvO9GWFO for ; Sat, 12 Aug 2017 21:05:34 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C26C45F3CE for ; Sat, 12 Aug 2017 21:05:33 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id x3so58679589oia.1 for ; Sat, 12 Aug 2017 14:05:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=U2PRPGO4UctcD6NylPIB1a+7uZBjmc1J/T0lDwOlpD0=; b=R7YwSzSKD76QC8ZGy+ntUzl+QTnyi6JTWMGP9tN4E63FJK/CJzadbeCV7HhUxxKURC byGY761zl8tlXeA7Gimk6OhLMvVcv77zBQHBy7nZdEDiD8CijTu/xpvgW0TjqCfUmEKk Jo/yuqpgLLVxxheBTHeBplsLDi17xrB47AjypEkQBoxux5j+fV4djMayKzkQOINT3QzL yKdBY0kNAF8l4AcRX3cyj3bFifxR17R0UuwpkSmRqWOKyYfgzQRI1nq539mJpDmUKmWI HKBCmiYOvXslXJn6Eo4QD+23/PnPPxz9gdKc9qAEQHhZ436xLZLtZXtT3gArCrzm5RwD FTEQ== X-Gm-Message-State: AHYfb5gxyk2Nj3966pGFRfL4+dtlq2aHtfgdBQe/c5Xvcqf1v0+gT4zQ Fk+UsKjCt4P4f4QYSmA0VIaFqA1KPP2U X-Received: by 10.202.66.11 with SMTP id p11mr23164982oia.267.1502571925540; Sat, 12 Aug 2017 14:05:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.171.131 with HTTP; Sat, 12 Aug 2017 14:05:25 -0700 (PDT) In-Reply-To: References: From: Justin Bertram Date: Sat, 12 Aug 2017 16:05:25 -0500 Message-ID: Subject: Re: [Artemis] - Can last value queue be sent to multiple consumers? To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113dd9a0df2931055694c910" archived-at: Sat, 12 Aug 2017 21:05:40 -0000 --001a113dd9a0df2931055694c910 Content-Type: text/plain; charset="UTF-8" What client protocol/API are you going to be using? I think you could accomplish what you're after by using a multicast address with multiple last-value queues which represent all your workstations. How you access those will depend on what protocol/API you decide to use. Justin On Fri, Aug 11, 2017 at 5:13 AM, Lionel van den Berg wrote: > Hi, > > I'm currently using activemq and now looking into Artemis. One of the > interest features I see is the is the last-value queue option. However what > I want to use it for is for regularly updating data and not so regular > updating data where the last value is always the only interesting value, > but where that data is interesting to multiple consumers. > > A bit more on my design thought in case I've missed another better > solution. I have many workstations that connect, disconnect and change user > role. They all use a sub-set of the same data that I want to publish to > dedicated queues (last value) or topics. When a workstation connects, I > want it to be able to get the most recent value immediately. I then want > them all to be receiving updates as they happen. I can solve it through > triggering a publish in the software when a new workstation connects, but > if the messaging system can help me then that is better. > > Thanks > > Lionel. > --001a113dd9a0df2931055694c910--