Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of jzimmerman@netflix.com
 designates 69.53.237.163 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024;d=netflix.com;
  h=from:to:subject:date:message-id:in-reply-to:content-type:mime-version;
  b=R9jv4YQZNz53AoDTQIyBndaDBtbL590uNEK70AdPdD2xH7qwP0smtyR84hMtYHyorOHf/WoA
    aWTKVIw2Afooj1r+mhwb05woOMh8w34BoDE0VIEb3Q0ScM/HUvYIaJ9t2jhAwC1/V/PQ0tXi
    fS5RV3fJq5bBHvgRhfyo1QBwwh4=
From: Jordan Zimmerman <jzimmerman@netflix.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>, Mike Schilli
	<m@perlmeister.com>
Subject: Re: SQS Implementation with ZooKeeper
Thread-Topic: SQS Implementation with ZooKeeper
Thread-Index: AQHMtEuZrTDVV7J83U6s+YxswRJGVpXPL/aA
Date: Tue, 6 Dec 2011 19:21:41 +0000
Message-ID: <CB03AB23.1117D%jzimmerman@netflix.com>
In-Reply-To: <alpine.LRH.2.02.1112061112390.4757@pyramidlake.corp.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.10.0.110310
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F9D311396C374A4F91284911C0B94322@netflix.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: None (exout102.netflix.com: jzimmerman@netflix.com does not
 designate permitted sender hosts)

Curator has both a Queue and a Priority Queue as described on the
ZooKeeper recipes page:

https://github.com/Netflix/curator/wiki/Recipes


-JZ

On 12/6/11 11:16 AM, "Mike Schilli" <m@perlmeister.com> wrote:

>Seems like it should be possible to implement a queue service like
>Amazon's SQS [1] with ZooKeeper, with queue items becoming 'invisible'
>once a client picks them, but pop back into the queue after a timeout
>unless the client doesn't explicitly delete them.
>
>Anyone done that?
>
>--=20
>-- Mike
>
>Mike Schilli
>m@perlmeister.com
>
>[1] http://aws.amazon.com/sqs
>