rapidsms/rapidsms — pull request #355 by copelco (2013-04-02 16:05:33+00:00)
Title: Catch exceptions in blocking router during send

We need to think about the best way for backends to handle outbound errors and how it should notify the router of one. Right now the CeleryRouter and DatabaseRouter will catch all exceptions, but BlockingRouter doesn't. In old-routing, backends use to sent a sent attribute and, I presume, catch all exceptions.

I like the idea of backends being able to throw exceptions and it won't kill the entire routing process, so I'm leaning towards just catching exceptions in BlockingRouter.

Duplicate of #352. PR against proper branch.