9 Commits (8bd613e9b8ffc012e9766d8255b9f77f6cbce809)

Author	SHA1	Message	Date
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	92506216d3	use common base class for jobs	8 years ago
Jan Sandbrink	b76c351813	Ensure mails are not sent twice ... ... in case a user is author + watcher	9 years ago
Jan Sandbrink	4ee163393f	Rearrange mail delivery responsibilities ... - each delivery job delivers only a single mail (like in the past) - a common super-class ensures correct handling of different error conditions (similar to the past) This new structure should allow for an efficient error handling: - fail the mail delivery on a per-recipient basis (i.e. redeliveries on error only affect the user that did not receive a mail) - only fail the delayed job for delivery errors (e.g. network issues, etc) - do not fail the delayed job for rendering errors (which are likely to re-occur on each rendering) -> only log those	9 years ago
Jan Sandbrink	dfb9a5cd20	remove remaining AR find_by_x finders ... - most of them were removed by @myabc in the rails4 branch - some where reintroduced due to parallel development to that branch - still some occurences left that will hit custom implementations	9 years ago
Jan Sandbrink	715c664cbe	generalize module included in all delayed jobs ... now also applies to other activities one might want to execute before all delayed jobs (as discussed with @ulferts)	9 years ago
Jan Sandbrink	10d61b01e7	let delayed jobs reset the request store ... This is especially neccessary since our Settings use the request store to determine, whether they need to invalidate the cache key. If the request store was never reset, the settings in our delayed jobs would be cached at an old value forever (until the next restart).	9 years ago
Jan Sandbrink	285b7f5437	move on-behalf-delivery into notification mailer	9 years ago
Jan Sandbrink	3b3ae3f6b3	split up mail delivery and enqueueing	9 years ago
Jan Sandbrink	974523c370	partly address an edge case that can prevent notification delivery ... "partly" because the current implementation is still "vulnerable" if the succeeding journal gets outdated in the same way as the preceeding one. The edge-case of the edge-case....	9 years ago
Jan Sandbrink	6c1e4dbf4f	send aggregated notifications ... - only sending the last mail of an aggregation chain - displaying the aggregated state of the change - replaces old classes for mail notifications - old special error handling for missing users is obsoleted, since recipients are determined at jobs runtime - special cases for missing author and journal are considered	9 years ago