in reply to Catalyst controller comparison fails in Root controller auto()

The reload "-r" option is probably the culprit. One should never use it in a production environment and dynamically [un|re]loading modules and controllers is a bit like cutting the branch you are sitting on.

Does the same thing happen if you run your application without the "-r" option?

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Replies are listed 'Best First'.
Re^2: Catalyst controller comparison fails in Root controller auto()
by smallvaluesof2 (Novice) on Jan 11, 2009 at 14:28 UTC

    I'm only using the -r option in development, but was initially alarmed at the possible prospect of similar behaviour in production, until I realized that Catalyst would never have become popular with that kind of instability so that the fault had to lie elsewhere (probably in my vicinity).

    Setting up a script to repeatedly submit an incorrectly completed registration page to Catalyst running without -r option for my reassurance.

    It seems like I was not following good practice, so will try an alternative way of achieving the same end.

    Thanks