RailsConf2008 の非同期処理に関する話題

RailsConf2008 で、Jonathern Dahl さんが Rails での非同期処理について話すみたいです

RailsConf 2008: Asynchronous Processing with Ruby on Rails

http://en.oreilly.com/rails2008/public/schedule/detail/1813

適当に訳すと...

Rails は HTTP リクエストな同期処理はいい感じにこなしてくれるけど、ちょっと複雑な処理や時間のかかる処理をしたいと思うと非同期処理が必要になる。だから非同期処理をはじめてみよう。ちょっと調べてみると、Rails で非同期するにはこんな方法がある。cron, BackgroundDRb, AP4R, daemons, そして AmazonSQS。実際の事例とコードを通じで、それぞれの良いとこ/悪いとこを順にみてみるよ。

ほとんど同じ内容ですが、こっちにもう少し詳しく書かれています。Jonathern と仲間うちのエンジニアで投稿しているサイトっぽいです。書籍の紹介とほかの非同期ライブラリ、starling, workling, beanstalk, spawn, background_fu あたりへの言及が増えてますね。
AP4R についてはどんな話をしてくれるんだろ... (^^;

Rail Spikes: See you at RailsConf '08

http://railspikes.com/2008/2/25/speaking-railsconf-2008

It looks like I will be speaking at RailsConf again. This time, I’ll be discussing asynchronous processing.
If you've worked on a Rails app that strays beyond basic CRUD, you've probably had to think about running some actions in the background – that is, outside of the HTTP request/response cycle. I've had to worry about this on quite a few projects, and contributed a recipe to the forthcoming Advanced Rails Recipes book. The recipe discussed how to package a Ruby script as a daemon, which is a simple and powerful approach to background processing. But there are quite a few others, including (but not limited to): AP4R, cron, starling, workling, beanstalk, backgroundrb, spawn, background_fu, and Amazon SQS. And I've left out quite a few.
So as I prepare for the conference, I'd love your feedback. What options have you tried? What has worked well or worked poorly? What would you like to see at the conference?

紹介されている書籍はこちら。Jonathern は "Asynchronous recipes" として、"Processing an Asynchronous Workflow" と "Off-Loading Long-Running Tasks to BackgrounDRb" というレシピを書いているみたいです。