Return-Path: X-Original-To: apmail-zookeeper-bookkeeper-user-archive@minotaur.apache.org Delivered-To: apmail-zookeeper-bookkeeper-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 29EC2DA30 for ; Sat, 29 Dec 2012 11:59:12 +0000 (UTC) Received: (qmail 38965 invoked by uid 500); 29 Dec 2012 11:59:12 -0000 Delivered-To: apmail-zookeeper-bookkeeper-user-archive@zookeeper.apache.org Received: (qmail 38804 invoked by uid 500); 29 Dec 2012 11:59:07 -0000 Mailing-List: contact bookkeeper-user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bookkeeper-user@zookeeper.apache.org Delivered-To: mailing list bookkeeper-user@zookeeper.apache.org Received: (qmail 38781 invoked by uid 99); 29 Dec 2012 11:59:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Dec 2012 11:59:06 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yannick.legros59@gmail.com designates 209.85.215.51 as permitted sender) Received: from [209.85.215.51] (HELO mail-la0-f51.google.com) (209.85.215.51) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Dec 2012 11:58:58 +0000 Received: by mail-la0-f51.google.com with SMTP id fj20so2039391lab.38 for ; Sat, 29 Dec 2012 03:58:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9eXusGljfQrO5LZzvetqPSEP22fUFmyqZWwmwJ673N0=; b=Xcu0numcY9DWrO5ohoLdWfjn63PYo38tlDuuwpgNYisBzRgvXm1X5CTIgvAWbq/Iyp 90D/dROTC3+AjEpiME/eu0SEacAb1tfD+q3073SOHgwnnTuQerq6/rXv4f7EVB7TDrxO Jt1u7tnoS5v4eEf6E9bn+AU+4BosmFvHJJG8VC4FhqaiMQirwfjV8ZhX9BSk5hI+cdDg lEm8YKCHyMjtipgkUPsxVb4vf2pl4tDc+DJxYvOPOS+r4IPB1q9xGs+YKooEEa6/5Q6V 0WUGGMESGIUCEWyiQIbpZLw+h6nzGePWXNJNCRpThh3sEPRbX6I1MUVJ9NQA41A1IckR kPVQ== MIME-Version: 1.0 Received: by 10.112.88.97 with SMTP id bf1mr14642733lbb.64.1356782318196; Sat, 29 Dec 2012 03:58:38 -0800 (PST) Received: by 10.112.6.103 with HTTP; Sat, 29 Dec 2012 03:58:38 -0800 (PST) In-Reply-To: References: Date: Sat, 29 Dec 2012 12:58:38 +0100 Message-ID: Subject: Re: hedwig question From: Yannick Legros To: bookkeeper-user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=bcaec554d60e1d190d04d1fc80e5 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554d60e1d190d04d1fc80e5 Content-Type: text/plain; charset=ISO-8859-1 thanks for your answer sijie. what i need is not exactly "subscribers be aware of messages publish before they subscribe" but "be sure that my message be consume by almost one subscriber" so if a publisher publish message on topics with no subscribers the first subscriber who will read the topics will get all published messages before his subscription. hope i was clear. Thanks, yannick. 2012/12/28 Sijie Guo > > does this is the default behaviour of hedwig? > > A subscriber would receive all the messages published after its first time > subscribe until it unsubscribe. > > so go back to your example: > > 1) if the subscriber subscribe T first time, it would only receive M2. > 2) if the subscriber already subscribe before M1. so the subscribe between > M1 and M2 is an attach subscribe, so it would receive M1 and M2 eventually > (if it doesn't receive M1 at its first time subscribe) > > > can we configure something (in subscription option for exemple) for > subscribers be aware of messages publish before they subscribe and not > consumed yet. > > Currently Hedwig doesn't support it. But I am just curious why a > subscriber need to be aware of messages published before they subscribed? > Is there any special case you are considering? > > -Sijie > > > On Fri, Dec 28, 2012 at 3:23 AM, Yannick Legros < > yannick.legros59@gmail.com> wrote: > >> Hello, >> >> I have just another question. >> >> in this case : >> >> publisher post a message M1 on topics T >> subscriber subscribe to T >> publisher post a message M2 on topics T >> >> when subscriber starts delivery he will get M2 but not M1 because he has >> subscribed after M1 was publish. >> >> does this is the default behaviour of hedwig? >> can we configure something (in subscription option for exemple) for >> subscribers be aware of messages publish before they subscribe and not >> consumed yet. >> >> thanks a lot. >> > > --bcaec554d60e1d190d04d1fc80e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
thanks for your answer sijie.

what i nee= d is not exactly=A0
=A0"subscribers be aware of messages pub= lish before they subscribe"=A0
but=A0
=A0"be = sure that my message be consume by almost one subscriber"

so if a publisher publish message on topics with no sub= scribers the first subscriber who will read the topics will get all publish= ed messages before his subscription.

hope i was cl= ear.

Thanks, yannick.

20= 12/12/28 Sijie Guo <guosijie@gmail.com>
>=A0does this is the default behaviour of hedwig?

A subscriber= would receive all the messages published after its first time subscribe un= til it unsubscribe.

so go back to your example:

1) if the subscriber subscribe T first time, it would only receive M2.
2) if the subscriber already subscrib= e before M1. so the subscribe between M1 and M2 is an attach subscribe, so = it would receive M1 and M2 eventually (if it doesn't receive M1 at its = first time subscribe)

>=A0can we configure something (in subscription option for exe= mple) for subscribers be aware of messages publish before they subscribe an= d not consumed yet.

Currently Hedwig doesn't support it. But I am just curious why a sub= scriber need to be aware of messages published before they subscribed? Is t= here any special case you are considering?

-Si= jie


On Fri, Dec 28, 2012 at 3:23 AM, Yannick Legros <yannick.legros59= @gmail.com> wrote:
Hello,

I have just another question.

in this case :

pu= blisher post a message M1 on topics T
subscriber subscribe to T
publi= sher post a message M2 on topics T

when subscriber starts delivery h= e will get M2 but not M1 because he has subscribed after M1 was publish.
does this is the default behaviour of hedwig?
can we configure somet= hing (in subscription option for exemple) for subscribers be aware of messa= ges publish before they subscribe and not consumed yet.

thanks a lot= .


--bcaec554d60e1d190d04d1fc80e5--