[Zope3-dev] DISCUSS: Designing for debuggability

[Martijn Faassen]

Paul Everitt wrote:
> But could Zope3 do more?  That is, could an architecture be put in place 
> that incepts the problem of debugging and scopes out some solutions?  A 
> component architecture that actively anticipates the needs of debugging 
> could help Zope be more competitive.  Of course, it's all in how it's 
> scoped.  Debugging can mean a lot of things.

It strikes me as possible that you could use the dreaded ';' in pathname
for an argument that indicates that the request is to be run through a
debugger (if you have permissions) from that point.

I.e. something like this:

http://localhost:8080/mypath/here/there;debug/foo/bar

Perhaps this is misusing these things. :)

This still wouldn't allow for TTW debugging by itself, which would be nice,
but would help making it easier to invoke. Ideally it could even load up your
debugger of choice, which might include a TTW version.. 

Another thing could be done with the tracebacks; there could be a mode
where you can click on a traceback and go to the line indicated. Of course
this has more security implications, but if we have TTW products, it
would definitely be feasible.

Some of the security implications of exposing innards to the web would 
become much less fearsome if Zope3 supported some encrypted protocols (such
as HTTPS) out of the box. Also interesting in that respect is a way to
spell 'I only want to enable this permission for this role if it's connected
through HTTPS' or somesuch.

Anyway, just dumping some random ideas.

Regards,

Martijn