sthzg / django-chatterbox Goto Github PK

This feature opens an important design decision about the nature of chatterbox events. When delivering a notification to multiple recipients of the same handler (e.g. 1 notification to multiple email addresses, 1 notification to multiple twitter accounts, etc.) should each notification be a separate record in the database?

A pro for this is, that it is the only sane way to keep error reporting constant. Think about a a notification that succeeds for on recipient and fails for the other one. After processing the notification, what's the status for it? (error, no error, partial error, etc.). As a direct result, the retry mechanism gets a lot more complicated, since it should only retry sending to 1/2 recipients.

The con is that revoking a pending notification involves more house keeping logic, since you need to cancel multiple rows that originated from the same event handler.