Notalib/LYT — Issue #39: Error handling
Author: simmoe
Created: 2011-12-17 08:25:19+00:00
State: open

There's basically two sorts of errors: incidents where we want to let the user know, and incidents where we want to log the error and go on.

Let the user know

Let's break it up: rpc errors, file handling errors and streaming errors.

RPC errors should generally be handled the same way that login errors are handled right now: try again - say three times, otherwise let the user know: It looks like we can't playback the audiobook right now. Please tru reloading the page. If the problem persists, check your internet connection or try again later. If the problem persists don't hesitate to contact us: support phonenbr.

File handling errors occur when - for some reason - we are not able to parse - say - an ncc correctly. The easiest way to check that is in fact to check if theres any items in the index - if not, some form of error occurred. Considering the state of the catalogue, there may be millions of reasons why this could happen. So we need the book-id to debug. Send a mail to the maintainer (ldh@nota.nu for now) and let the user know, there was a problem parsing this book.

Streaming errors - probably occur because of either lost connection or some logoff in the background (i.e. if the user switch IP). Try logging in and continue playback. If the connection is lost (is there anyway to check that), let the user know

Log the error

If there are interface errors or errors concerning parsing of books or files that don't affect playback, we want to know - but we don't want the user to know. I think email is an easy to implement sollution - we get the error and can check it out right away.