[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Meeting. March 3rd. Reuven Lerner
On Sun, 20 Feb 2000, Alex Shnitman wrote:
> I'd most like to hear about development environments and techniques
> for developing web applications.
[...]
> -- but how do you do all this when you're writing code
> that's going to run under a web server and you can't run it frontally?
i think you've hit an exposed nurve here... i'd be very surprised to hear
about such a tool that exists for web development. i would guess, however,
that debugging this simply requires some imagination, and a design that is
easy for debugging. for example, with a large-scale application, you'll
most likely use a back-end that runs as a daemon, with CGI scripts
communicating with it, thus keeping the CGIs simple, and allowing you to
debug that daemon just like you'd debug any unix daemon - attaching a
debugger after it's launched, or running it in the forground for debugging
sessions, rather then as a daemon.
another possible trick - add some sleep to the startup of a cgi, and use
that time to attach a debugger to it (question - can one attach the perl
debugger to an already-running program? what about a script running inside
a perl module? is it supported by the perl debugger?)
one more thing - CGIs get all their input from stdin and the environment.
thus, they can be debugger by launching them from the command line, with
proper setting of the relevant environment variables, and just walking
through.
thought none of these options is ideal.
guy
"For world domination - press 1,
or dial 0, and please hold, for the creator." -- nob o. dy
PGP signature