Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Chris Behrens
I have been meaning to reply with the exact same thing. On Feb 18, 2011, at 10:12 AM, Jay Pipes wrote: > Personally, I'd prefer C++ since that's what I'm used to, but I'd be > open to learning Erlang, too. Been wanting to learn it for a while > now. > > -jay > > On Fri, Feb 18, 2011 at 1:11 AM

Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Eric Day
Hi Mike, On Sat, Feb 19, 2011 at 07:42:12PM -0600, Michael Barton wrote: > On Fri, Feb 18, 2011 at 9:38 PM, Eric Day wrote: > > Hi Mike, > > > > You make a good point, I apologize for not documenting some of the > > ideas sooner. The architecture I had in mind borrows from other > > queue systems

Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Michael Barton
On Fri, Feb 18, 2011 at 9:38 PM, Eric Day wrote: > Hi Mike, > > You make a good point, I apologize for not documenting some of the > ideas sooner. The architecture I had in mind borrows from other > queue systems I've worker on, along with feedback I've gotten from > various conversations while ge

Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Eric Day
Hi Todd, That's the multicast example, for a normal 1-1 queue, look at the first example: Worker: POST /account/queue?wait=60&hide=60&detail=all (long-polling worker, request blocks until a message is ready) Client: PUT /account/queue (message inserted, returns unique id that was created) Wor

Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Eric Day
When you want to modify messages in a queue and also return those that were modified. This is the atomic get/set needed by workers. POST /account/queue?hide=60 HTTP/1.1 This will return all messages currently in /account/queue, but also mark them as hidden for 60 seconds. This ensures only one wo

Re: [Openstack] Queue Service, next steps

2011-02-19 Thread Eric Day
Hi Mark, On Sat, Feb 19, 2011 at 11:18:26AM -0500, Mark Washenberger wrote: > It seems like put and post on ../queue[/id] are reversed from the usual > sense. I am probably just not familiar with the idioms for previous queue > services, but I imagine the following scheme. > >  POST .../queue

Re: [Openstack] Nova-core membership request

2011-02-19 Thread Paul Voccio
+1 One more. On 2/18/11 9:15 PM, "Ed Leafe" wrote: >On Feb 18, 2011, at 6:07 PM, Rick Harris wrote: > >> Throwing my hat into the ring for nova-core membership. Eager to help >>knock down that merge-prop backlog we have at the moment :-) > >+1 > > >-- Ed Leafe > > > > >___