Support enqueue_in/enqueue_at? about activejob HOT 9 CLOSED

👍

from activejob.

See https://twitter.com/dhh/status/468349205392924672

from activejob.

Didn't know support was that wide. I'd say it's worth considering support for this, then.

from activejob.

(I just don't want ActiveJob to have to know anything about or have any infrastructure for future jobs, beyond passing params to the queues).

from activejob.

We could create separate gems to extend activejob to support future jobs or
event recurring jobs

Cristian Bica

On Mon, May 19, 2014 at 2:48 PM, David Heinemeier Hansson <
[email protected]> wrote:

(I just don't want ActiveJob to have to know anything about or have any
infrastructure for future jobs, beyond passing params to the queues).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-43492421
.

from activejob.

One pattern to look at is how we deal with expires_in on the AS caching infrastructure. I don’t believe all the caching backends support that either. Maybe it can help inform.

I’d rather not have a separate gem just to pass a few params.

On May 19, 2014, at 1:48 PM, Cristian Bica [email protected] wrote:

We could create separate gems to extend activejob to support future jobs or
event recurring jobs

Cristian Bica

On Mon, May 19, 2014 at 2:48 PM, David Heinemeier Hansson <
[email protected]> wrote:

(I just don't want ActiveJob to have to know anything about or have any
infrastructure for future jobs, beyond passing params to the queues).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-43492421
.

—
Reply to this email directly or view it on GitHub.

from activejob.

https://github.com/chanks/que also supports job scheduling.

from activejob.

Sucker punch uses the built-in Celluloid timing API: https://github.com/brandonhilkert/sucker_punch/blob/master/README.md#perform-in

from activejob.

wip at #35. closing

from activejob.