Skip to content
This repository has been archived by the owner on Nov 17, 2017. It is now read-only.

Queue per action #2

Open
joelvh opened this issue Apr 20, 2013 · 3 comments
Open

Queue per action #2

joelvh opened this issue Apr 20, 2013 · 3 comments

Comments

@joelvh
Copy link

joelvh commented Apr 20, 2013

I'm new to qe, but am wondering if it's possible to specify a queue per action so that not all actions run against the same queue?

@fnando
Copy link
Owner

fnando commented Apr 21, 2013

You can set the queue name on your worker by using the Qe::Worker.queue method.

class MailWorker
include Qe::Worker
queue :mail
end

Nando Vieira
http://nandovieira.com.br

On 19/04/2013, at 23:12, Joel Van Horn notifications@github.com wrote:

I'm new to qe, but am wondering if it's possible to specify a queue per action so that not all actions run against the same queue?


Reply to this email directly or view it on GitHub.

@joelvh
Copy link
Author

joelvh commented Apr 21, 2013

Hi @fnando, that allows you to specify a queue at the class level, which is used for all actions? If I want to put all my worker methods in one class, it would be nice to specify a different queue name inside the action method, which would be at the instance level. Maybe having that ability goes against how the worker classes are meant to be designed.

@fnando
Copy link
Owner

fnando commented Apr 22, 2013

Oh, I see what you mean. For now, your best option is creating a new worker. But I understand that'd be nice to set the queue name per action.

I'll look into that when I have the time.

Nando Vieira
http://nandovieira.com.br

On 21/04/2013, at 15:57, Joel Van Horn notifications@github.com wrote:

Hi @fnando, that allows you to specify a queue at the class level, which is used for all actions? If I want to put all my worker methods in one class, it would be nice to specify a different queue name inside the action method, which would be at the instance level. Maybe having that ability goes against how the worker classes are meant to be designed.


Reply to this email directly or view it on GitHub.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants