Trihedralguy has asked for the wisdom of the Perl Monks concerning the following question:

I know the Apache:ASP group might be better to post this question, but I figured I would give PerlMonks a try, as they are typically smart about all things. :)

Anyway, I just started making some pages with Apache:ASP and I really like what it brings to the table. However, I must be doing something wrong because sometimes if I have a compile time error the page is "cached" with an error.

So what ends up happening is when i refresh the page after correcting the error, sometimes it will fetch the cached page with the error and give an error, other times it will print the page with the current code (as it should!)

I'm not sure what to do, I've looked through the documentation and tried setting something like "PerlSetVar NoCache".

Any suggestions?

One side note: I'm using Perl DBI with Apache ASP and it seems that sometimes the errors stem from doing so, maybe like its not caching the connection of some sorts.

Thanks for any assistance :)

Replies are listed 'Best First'.
Re: Apache::ASP Question
by Trihedralguy (Pilgrim) on Oct 19, 2009 at 21:29 UTC
    I think this is what I might need:

    StatINC
    default 0, if true, reloads perl libraries that have changed on disk automatically for ASP scripts. If false, the www server must be restarted for library changes to take effect.

    A known bug is that any functions that are exported, e.g. confess Carp qw(confess), will not be refreshed by StatINC. To refresh these, you must restart the www server.

    This setting should be used in development only because it is so slow. For a production version of StatINC, see StatINCMatch.

       PerlSetVar StatINC 1

    I havent had the chance to test yet, apparently I need to install a module first.
[reply]

Back to Seekers of Perl Wisdom