seancribbs/ripple — comment on commit e5f24a5d54cd1f8f3bac3354cbbbd0c71b8a8d6d
File:  line 0
By aphyr:

Case 1: transport-level (i.e. connection) errors. I can't imagine a case in which a library would introduce a connection-level exception which couldn't be added by NETWORK_ERRORS << ExceptionClass.

Case 2: Logical errors like mapreduce, HTTPFailed request, etc. If you were to rescue them here, they will fuck shit up, as detailed above. We should invent a standardized system for retrying logical errors at a higher level, if that's desirable. Open to ideas... @seancribbs and I have talked about this a few times. Thoughts?