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 5EA07200C00 for ; Wed, 18 Jan 2017 17:01:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5D1D6160B3A; Wed, 18 Jan 2017 16:01:12 +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 7BBD5160B34 for ; Wed, 18 Jan 2017 17:01:11 +0100 (CET) Received: (qmail 91940 invoked by uid 500); 18 Jan 2017 16:01:10 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 91930 invoked by uid 99); 18 Jan 2017 16:01:10 -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; Wed, 18 Jan 2017 16:01:10 +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 1CD841804B1 for ; Wed, 18 Jan 2017 16:01:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.174 X-Spam-Level: **** X-Spam-Status: No, score=4.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, HTML_MESSAGE=2, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=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 i1KpGwjteD-E for ; Wed, 18 Jan 2017 16:01:08 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3383F5F282 for ; Wed, 18 Jan 2017 16:01:08 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id E7EB33AA30F4 for ; Wed, 18 Jan 2017 07:43:39 -0800 (PST) Date: Wed, 18 Jan 2017 09:01:07 -0700 (MST) From: afedotov To: user@ignite.apache.org Message-ID: In-Reply-To: <1484712217434-10109.post@n6.nabble.com> References: <1484712217434-10109.post@n6.nabble.com> Subject: Re: How can we create a TOPIC Config? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_103770_852917867.1484755267347" archived-at: Wed, 18 Jan 2017 16:01:12 -0000 ------=_Part_103770_852917867.1484755267347 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Did I get you correct, that you want to send an update to a topic every time the cache is updated? If that is the question then I would suggest you taking a look at the following: https://apacheignite.readme.io/docs/events https://apacheignite.readme.io/docs/messaging On Wed, Jan 18, 2017 at 7:03 AM, hitendrapratap [via Apache Ignite Users] < ml-node+s70518n10109h13@n6.nabble.com> wrote: > I have small local cache(populate the cache when application starts). When > I will get an update for the same then I want to publish a updated message > to a topic. So now all the client and server will receive the updated > message as they were registered listener to that topic. > I am trying to configure the same like creating a topic config where i can > specify topic name and listener implementation? > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/How-can- > we-create-a-TOPIC-Config-tp10109.html > To start a new topic under Apache Ignite Users, email > ml-node+s70518n1h65@n6.nabble.com > To unsubscribe from Apache Ignite Users, click here > > . > NAML > > -- Kind regards, Alexander. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-can-we-create-a-TOPIC-Config-tp10109p10118.html Sent from the Apache Ignite Users mailing list archive at Nabble.com. ------=_Part_103770_852917867.1484755267347 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
Hi,

Did I get you correct, that you wan= t to send an update to a topic every time the cache is updated?
If that = is the question then I would suggest you taking a look at the following:



On Wed, Jan 1= 8, 2017 at 7:03 AM, hitendrapratap [via Apache Ignite Users] <[hidden email]> wrote:
=09I have small local cache(populate the cache when application starts). Wh= en I will get an update for the same then I want to publish a updated messa= ge to a topic. So now all the client and server will receive the updated me= ssage as they were registered listener to that topic.=20
I am trying to configure the same like creating a topic config where i = can specify topic name and listener implementation? =09 =09 =09 =09
=09
=09
=09
=09=09
If you reply to this email, your mess= age will be added to the discussion below:
=09=09http://apache-ignite-users.70518.x6.nabble.com/How-can-<= wbr>we-create-a-TOPIC-Config-tp10109.html =09
=09
=09=09To start a new topic under Apache Ignite Users, email [hidden email]
=09=09To unsubscribe from Apache Ignite Users, click here.
=09=09NAML =09



--
Kind regards,
Alexander.
=09 =09 =09
View this message in context: Re: How c= an we create a TOPIC Config?
Sent from the A= pache Ignite Users mailing list archive at Nabble.com.
------=_Part_103770_852917867.1484755267347--