Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
7.1.5.1 25 Dec 2024 19:16:49
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.5.1
Changes: https://github.com/rails/rails/releases |
7.1.5 21 Nov 2024 13:39:37
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.5
Changes: https://github.com/rails/rails/releases |
7.1.4.2 26 Oct 2024 23:28:38
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.4.2
Changes: https://github.com/rails/rails/releases |
7.1.4.1 22 Oct 2024 09:50:47
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.4.1
Changes: https://github.com/rails/rails/releases |
7.1.4 18 Sep 2024 06:15:11
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.4
Changes: https://github.com/rails/rails/releases |
7.1.3.4 06 Jun 2024 07:48:22
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.3.4
Changes: https://github.com/rails/rails/releases |
7.1.3.3 19 May 2024 22:13:24
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.3.3
Changes: https://github.com/rails/rails/releases |
7.1.3.2 09 Mar 2024 14:07:02
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.3.2
Changes: https://github.com/rails/rails/releases |
7.1.3 21 Feb 2024 15:11:00
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.3
Changes: https://github.com/rails/rails/releases |
7.1.2 14 Nov 2023 17:16:35
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Update to 7.1.2
Changes: https://github.com/rails/rails/releases |
7.1.1 01 Nov 2023 07:56:03
    |
Po-Chuan Hsieh (sunpoet)  |
devel/rubygem-activejob71: Add rubygem-activejob71 7.1.1
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. |