4 Commits

Author	SHA1	Message	Date
Bharat Mediratta	bc13659d37	Remove cruft from API	2009-03-04 08:55:41 +00:00
Bharat Mediratta	23b0abb974	Redefine the batch API to be very very simple. You call ... batch::start() before starting a series of events, and batch::stop() when you're done. In batch mode, the notification module will store up pending notifications. When the batch job is complete, it'll send a single digested email to each user for all of her notifications. Updated the scaffold and local_import to use this. Haven't modified SimpleUploader yet.	2009-03-04 08:51:49 +00:00
Tim Almdal	b7a72825af	Remove the === false and === true checks ... I really mean it this time	2009-03-03 06:26:12 +00:00
Tim Almdal	7cadb4b21b	Refactored the batch Api: 1) created a small batch helper class: ... Starting a batch call batch::operation(name, item). In the case of adding photos name = add and item is the parent of the new items. When the operation is finished the batch::end_operation(name) is called. operation and end_operation events are called. Handlers (i.e. item_created) can call batch::in_progress(name) to determine if a batch is being processed.	2009-03-03 05:59:38 +00:00