librelist archives

« back to archive

Job Status/Conventions

Job Status/Conventions

From:
Aaron Quint
Date:
2010-01-12 @ 22:14
Hey All

I realized after all, I could extract the 'long job' status stuff I'm
working on into a separate gem that wraps Resque job creation. In
terms of releasing a Resque 'plugin' what do people think about naming
conventions? Is it better for the gem to use its own namespace (aka
LongJob) that depends on or includes Resque? or is it better to put
the class inside of the Resque module (Resque::LongJob). I realize
this is really just a style preference but wondering what this
burgeoning community prefers.

--AQ

Aaron Quint
http://www.quirkey.com

Re: [resque] Job Status/Conventions

From:
Chris Wanstrath
Date:
2010-01-12 @ 22:19
On Tue, Jan 12, 2010 at 2:14 PM, Aaron Quint <aaron@quirkey.com> wrote:

> I realized after all, I could extract the 'long job' status stuff I'm
> working on into a separate gem that wraps Resque job creation. In
> terms of releasing a Resque 'plugin' what do people think about naming
> conventions? Is it better for the gem to use its own namespace (aka
> LongJob) that depends on or includes Resque? or is it better to put
> the class inside of the Resque module (Resque::LongJob). I realize
> this is really just a style preference but wondering what this
> burgeoning community prefers.

I like Resque::LongJob, unless it will work without Resque (say, with
DelayedJob or something).

-- 
Chris Wanstrath
http://github.com/defunkt

Re: [resque] Job Status/Conventions

From:
Aaron Quint
Date:
2010-01-12 @ 22:24
Cool. It makes heavy use of Redis so I think supporting DJ would be
kind of pointless.
--AQ

Aaron Quint
http://www.quirkey.com



On Tue, Jan 12, 2010 at 5:19 PM, Chris Wanstrath <chris@ozmm.org> wrote:
> On Tue, Jan 12, 2010 at 2:14 PM, Aaron Quint <aaron@quirkey.com> wrote:
>
>> I realized after all, I could extract the 'long job' status stuff I'm
>> working on into a separate gem that wraps Resque job creation. In
>> terms of releasing a Resque 'plugin' what do people think about naming
>> conventions? Is it better for the gem to use its own namespace (aka
>> LongJob) that depends on or includes Resque? or is it better to put
>> the class inside of the Resque module (Resque::LongJob). I realize
>> this is really just a style preference but wondering what this
>> burgeoning community prefers.
>
> I like Resque::LongJob, unless it will work without Resque (say, with
> DelayedJob or something).
>
> --
> Chris Wanstrath
> http://github.com/defunkt
>

Re: [resque] Job Status/Conventions

From:
Aaron Quint
Date:
2010-01-19 @ 21:45
For all those interested: finally pushed/open sourced this little gem
in question:

http://github.com/quirkey/resque-status

--AQ

Aaron Quint
http://www.quirkey.com



On Tue, Jan 12, 2010 at 5:24 PM, Aaron Quint <aaron@quirkey.com> wrote:
> Cool. It makes heavy use of Redis so I think supporting DJ would be
> kind of pointless.
> --AQ
>
> Aaron Quint
> http://www.quirkey.com
>
>
>
> On Tue, Jan 12, 2010 at 5:19 PM, Chris Wanstrath <chris@ozmm.org> wrote:
>> On Tue, Jan 12, 2010 at 2:14 PM, Aaron Quint <aaron@quirkey.com> wrote:
>>
>>> I realized after all, I could extract the 'long job' status stuff I'm
>>> working on into a separate gem that wraps Resque job creation. In
>>> terms of releasing a Resque 'plugin' what do people think about naming
>>> conventions? Is it better for the gem to use its own namespace (aka
>>> LongJob) that depends on or includes Resque? or is it better to put
>>> the class inside of the Resque module (Resque::LongJob). I realize
>>> this is really just a style preference but wondering what this
>>> burgeoning community prefers.
>>
>> I like Resque::LongJob, unless it will work without Resque (say, with
>> DelayedJob or something).
>>
>> --
>> Chris Wanstrath
>> http://github.com/defunkt
>>
>

Re: [resque] Job Status/Conventions

From:
Chris Wanstrath
Date:
2010-01-20 @ 05:40
On Tue, Jan 19, 2010 at 1:45 PM, Aaron Quint <aaron@quirkey.com> wrote:

> For all those interested: finally pushed/open sourced this little gem
> in question:
>
> http://github.com/quirkey/resque-status

Looks cool, thanks for releasing it!

Chris