./devel/ruby-activejob42, Job classes that can be run by a variety of queueing backends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 4.2.8, Package name: ruby23-activejob-4.2.8, Maintainer: minskim

Active Job is a framework for declaring jobs and making them run on a
variety of queueing backends. These jobs can be everything from
regularly scheduled clean-ups, to billing charges, to
mailings. Anything that can be chopped up into small units of work and
run in parallel, really.

It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for
running later. That's one of the most common jobs in a modern web
application: Sending emails outside of the request-response cycle, so
the user doesn't have to wait on it.

The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate
runner". We can then have framework features and other gems build on
top of that, without having to worry about API differences between
Delayed Job and Resque. Picking your queuing backend becomes more of
an operational concern, then. And you'll be able to switch between
them without having to rewrite your jobs.


Required to run:
[lang/ruby23-base] [devel/ruby-activesupport42]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 5743c76b7ebcb91e93c6ed1af3bf97e5888253fa
RMD160: 66abbebf9b2068a7d29047b4fe2eeab9f937617a
Filesize: 19 KB

Version history: (Expand)


CVS history: (Expand)


   2017-04-21 23:20:33 by Min Sik Kim | Files touched by this commit (4)
Log message:
Import ruby-activejob-4.2.8 as devel/ruby-activejob42

Active Job is a framework for declaring jobs and making them run on a
variety of queueing backends. These jobs can be everything from
regularly scheduled clean-ups, to billing charges, to
mailings. Anything that can be chopped up into small units of work and
run in parallel, really.

It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for
running later. That's one of the most common jobs in a modern web
application: Sending emails outside of the request-response cycle, so
the user doesn't have to wait on it.

The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate
runner". We can then have framework features and other gems build on
top of that, without having to worry about API differences between
Delayed Job and Resque. Picking your queuing backend becomes more of
an operational concern, then. And you'll be able to switch between
them without having to rewrite your jobs.