rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Job consumer logs to Rails.logger by default	Jeremy Kemper	2012-10-26	1	-0/+1
\|
*	Test that a Rails.queue consumer is automatically started in production	Jeremy Kemper	2012-10-13	1	-1/+11
\|
*	Backpedal from class-oriented config.queue. Set an actual queue instance.	Jeremy Kemper	2012-10-12	1	-3/+3
\|
*	Remove the queue container. Premature consolidation. Set up and maintain ↵	Jeremy Kemper	2012-10-12	1	-6/+6
\| \| \| \|	queues in the classes that use them instead.
*	ActiveSupport::SynchronousQueue doesn't have the drain method.	Rafael Mendonça França	2012-10-12	1	-4/+4
\| \| \| \| \|	Now we are using teh SynchronousQueue in the test environment instead of the TestQueue
*	Move the TestQueue tests to the proper file	Rafael Mendonça França	2012-10-12	1	-47/+0
\|
*	Immediately run queued jobs in tests. Otherwise you have to explicitly drain ↵	Jeremy Kemper	2012-10-12	1	-3/+3
\| \| \| \|	the queue to actually deliver your emails.
*	In development and test we drain the jobs in the same thread.	Rafael Mendonça França	2012-09-18	1	-4/+4
\|
*	Move queue classes to ActiveSupport	Santiago Pastorino	2012-09-14	1	-8/+8
\|
*	Use the SynchronousQueue as default in production and development.	Rafael Mendonça França	2012-09-12	1	-5/+6
\| \| \| \| \|	We should not let the users use the ThreadedConsumer without know about the risks
*	Remove unused require.	kennyj	2012-08-29	1	-1/+0
\|
*	Fixes wrong test class names.	kennyj	2012-08-29	1	-1/+1
\|
*	adding Rails::Queueing::Container	Aaron Patterson	2012-07-19	1	-5/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This allows us to do: In your configuration: Rails.queue[:image_queue] = SomeQueue.new Rails.queue[:mail_queue] = SomeQueue.new In your app code: Rails.queue[:mail_queue].push MailJob.new Both jobs pushed to the same default queue Rails.queue.push DefaultJob.new Rails.queue[:default].push DefaultJob.new
*	Ensure jobs do not refer to the queue	Paul Battley	2012-07-03	1	-0/+15
\| \| \| \| \| \| \| \|	Jobs pushed to the queue should not contain a reference to it. As the queue itself cannot be marshalled, and as a consequence of checking the marshallability of all jobs in the test environment, we can now guarantee this to be the case in the test environment when using the default TestQueue implementation.
*	Ensure test jobs are marshallable	Paul Battley	2012-07-03	1	-8/+28
\| \| \| \| \| \| \| \| \| \|	By marshalling and unmarshalling jobs when adding them to the test queue, we can ensure that jobs created during test runs are valid candidates for marshalling, and, thus, that they can be used with queueing backends other than the default simple in-process implementation. This will also be used in a subsequent commit to ensure that jobs pushed to the queue do not contain a reference to the queue itself.
*	Track queue threading with named classes	Paul Battley	2012-07-03	1	-14/+24
\| \| \| \| \| \| \|	Using an anonymous class prevented marshalling: we're not doing that yet, but the next commit will introduce this. This also provided an opportunity to improve the expressivity of the tests and to make the assertion failure messages clearer.
*	Allow configuring a different queue consumer	Carlos Antonio da Silva	2012-05-04	1	-3/+36
\| \| \| \| \| \|	Also make sure to not use default queue consumer with custom queue implementation. It is up to the new queue implementation to start / shutdown the consumer.
*	Removing unused local vars in Queue tests	Rodrigo Pavano	2012-05-01	1	-2/+0
\|
*	Use Rails::Queueing::Queue instead of Queue so people can build their own ↵	José Valim	2012-04-28	1	-2/+2
\| \| \| \|	consumers around stdlib's Queue
*	Fix failing test, TestQueue#contents is not #jobs	Carlos Antonio da Silva	2012-04-27	1	-1/+1
\|
*	Missing git add :trollface:	Yehuda Katz	2012-04-26	1	-0/+114