Re: [cgiapp] sticky parameters: Is CGI really to blame?

["Cees Hek" <suppressed>]

On 3/22/06, Sergej Zoubok <suppressed> wrote:
> I'll check this out, thanks! In the meantime, I've added some logging
> statments using the LogDispatch plugin to get a better view of the
> data flow through my app.

Hi Sergej,

Not sure if you found this in the LogDispatch docs, but it can really
simplify tracing the flow of you rapplication using the
LOG_METHOD_EXECUTION option.

__PACKAGE__->log_config(
    LOG_DISPATCH_MODULES => [
        {        module => 'Log::Dispatch::Screen',
                   name => 'screen',
                 stderr => 1,
              min_level => 'debug',
         append_newline => 1
        }
    ],
    LOG_METHOD_EXECUTION => [qw(__PACKAGE__ CGI::Application Other::Module)],
);

That will add an entry to your log at the start and end of every
method/sub call in the modules listed.  It also includes the
parameters that are passed into and returned from the calls.

This might actually make a nice addition to the DevPopup plugin. 
Provide a nice HTML tree of the execution path that your app took on
the last request...

Cheers,

Cees

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed