in reply to CGI and persistent data

CGI::Application::PLugin::Session + Data::Dumper can do the trick?

You can dump the variables to the session and then eval them each time. If you're using CGI::App you can even use cgiapp_prerun / cgiapp_postrun to handle the dump/eval to/from session and set the values as parameters on CGI::App.

That way, you only need to get/set the values as params from the $self (or whatever you use to represent your CGI::App object). That sounds simple and clean for me.

Replies are listed 'Best First'.
Re^2: CGI and persistent data
by stevieb (Canon) on Aug 28, 2009 at 00:23 UTC

    Thanks for the feedback...

    I despise having to create a 'GUI' for what I'm doing, as I'd much prefer to leave things cli-only (wouldn't most of us). Although I have no experience or understanding of 'session' regarding HTTP, I'll take a look at what you've suggested, and review the docs for the Session module.

    ...my question regarding the exploitation of the Perl garbage collection remains however, and it would be interesting to get feedback on that...

    -sb

[reply]

In Section Seekers of Perl Wisdom