Re: [Waterken-server] Debugging errors in the server

[Tyler C. <ty...@wa...>]

On May 27, 2006, at 10:04 PM, Sandro Magi wrote:
> This is just a general question regarding how you debug the waterken
> server. The .NET implementation is at the point where I can load code,
> browse the web of closures and invoke them, but there are still plenty
> of kinks to work out.

Wow, that's a major milestone. Good work.

> The way errors are reported made some of it difficult: some of the
> exceptions were more "fatal" and displayed debugging output right in
> the browser (the default ASP.NET behaviour for uncaught exceptions),
> but some were caught and saved in the database as the result of the
> request. Unfortunately, at the time I couldn't browse the links
> produced, so I was stuck using the debugger to read the stack traces.
>
> So Tyler, if you have some suggestions for debugging, or if there is a
> recommended way to catch and display/report errors, I'm all ears. :-)

I try to bubble errors all the way up to the response web page and just 
use the browser for debugging. With the power to traverse the object 
graph and invoke arbitrary closures, I find the browser is more 
powerful than most debuggers I've used.

Tyler

---
The web-calculus is the union of REST and capability-based security:
http://www.waterken.com/dev/Web/