Backend Exception Handling

[PhantomLel]

In the case that a request fails because of perhaps invalid request params or room does not exist or whatever, we should have an event sent to the client detailing the exception.

event 'event_error'
{
   msg : "some message to tell what went wrong"
}

This is important because it is quite annoying to debug by using print statements! If something goes wrong, we need to tell the client that something has went wrong so that a message can be displayed or something. Whenever a non-custom exception is encountered, it probably should just send back a default message, but if a custom exception is triggered, we should send back some custom message probably.

[clayrock78]

@PhantomLel

Do we want to close this issue? Is this still a problem for you or did we end up solving it?

[PhantomLel]

I think we still need to work on getting exceptions for all the different possible cases.

[clayrock78]

Okay, I am not sure how you want these exceptions to work. If you have anything specific in mind, could you lay it out? If not, we can discuss it.