From c47d6b499078b13cc7a75f520757b78c1a52d852 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Mon, 19 May 2014 13:01:33 +0200 Subject: Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dbd31d91ce..1b9e20c0d0 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ of queueing backends. These jobs can be everything from regularly scheduled clean-ups, billing charges, or mailings. Anything that can be chopped up into small units of work and run in parallel, really. -It also serves as the backend for ActionMailer's #deliver_later functionality +It also serves as the backend for [ActionMailer's #deliver_later functionality][https://github.com/rails/activejob/issues/13] 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. @@ -34,7 +34,7 @@ That's it! ## GlobalID support -Active Job supports GlobalID serialization for parameters. This makes it possible +Active Job supports [GlobalID serialization][https://github.com/rails/activemodel-globalid/] for parameters. This makes it possible to pass live Active Record objects to your job instead of class/id pairs, which you then have to manually deserialize. Before, jobs would look like this: -- cgit v1.2.3