+1 on the concept ... I feel that Rails has been without this for a
while. With the recent surge of activity on queue services, I think
this is an awesome suggestion ... it would be great to have a standard
Rails-ish way of setting up multiple work queues.
I think that a good starting point for wh
On Mon, Nov 23, 2009 at 10:17 AM, Chad Woolley wrote:
> On Sun, Nov 22, 2009 at 5:48 AM, Mikel Lindsaar
> wrote:
> > So, I have integrated edge ActionMailer with the Mail gem, removing TMail
> in
> > the process.
> > Currently, ActionMailer is running with 131 tests, 309 assertions, 0
> > failure
I want to take a moment to talk about the notion of a queue
abstraction layer in Rails and put a stake in the ground with my
opinions on the topic while at the same time getting some feedback.
My understanding is this: at the moment ActiveWorker (which can be
seen in this repo: http://github.com/j
On Sun, Nov 22, 2009 at 5:48 AM, Mikel Lindsaar wrote:
> So, I have integrated edge ActionMailer with the Mail gem, removing TMail in
> the process.
> Currently, ActionMailer is running with 131 tests, 309 assertions, 0
> failures, 0 errors
> This is using ActionMailer from http://github.com/mikel
So, I have integrated edge ActionMailer with the Mail gem, removing TMail in
the process.
Currently, ActionMailer is running with 131 tests, 309 assertions, 0
failures, 0 errors
This is using ActionMailer from http://github.com/mikel/rails as well as the
Mail gem version 1.2.8
But mail is throwi
