summaryrefslogtreecommitdiff
path: root/devel/rubygem-activejob-gitlab/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'devel/rubygem-activejob-gitlab/pkg-descr')
-rw-r--r--devel/rubygem-activejob-gitlab/pkg-descr16
1 files changed, 16 insertions, 0 deletions
diff --git a/devel/rubygem-activejob-gitlab/pkg-descr b/devel/rubygem-activejob-gitlab/pkg-descr
new file mode 100644
index 000000000000..d618ca834e3c
--- /dev/null
+++ b/devel/rubygem-activejob-gitlab/pkg-descr
@@ -0,0 +1,16 @@
+Active Job is a framework for declaring jobs and making them run on a variety of
+queuing 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.
+
+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 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.