Improved error/debug handling and /profiling for non-interactive requests

[WanWizard]

The current options with regard to debugging, profiling and error handling all leave from the premise that you have a browser to your disposal, i.e. they all display data in the output stream.

Obviously, this doesn't work for REST calls, HMVC calls, and is cumbersome for CLI code.

This was originally discussed here: https://github.com/fuel/core/pull/985

[marcopax]

I saw that the issue is still opened, any idea about the possible solutions? Or just an idea? I think that we can follow your original idea: returning an error in the right form (json, xml or something else).

I know that there are some logic implication with it, but I think it would be better then throw an exception and break the user experience with an error. A developer can handle the error, for example an ajax error, and manage the behavior.

[WanWizard]

Ideally I would like to have a server-side debugger, that runs on a separate URL, that follows the application live. And not produce any feedback to the current request, browser or not (I hate it when it ruins my page layout).

I have some idea's on how to go about it (node.js comes to mind), but I would really like to implement this in a package, without external dependencies.