At 05:40 AM 9/5/2003, Dimitris Papaharisis wrote:
a question of style (and maybe functionality).
What is the recommended way of linking to other modules / runmodes.
Is GET
good enough or should I be using POSTs?
and when I went to the next mode, a GET was performed and all the
params
where in
a little because it's not really one of my VALID run modes, but
declaring it with $self-run_modes() means that if someone calls my app
with rm=AUTOLOAD CGI::App thinks it's a valid run-mode.
If someone calls your run mode? Isn't the programmer the one who sets
up the rm= URL or form query info?
In article [EMAIL PROTECTED], Adam Gent wrote:
What is the recommended way of linking to other modules / runmodes. Is GET
good enough or should I be using POSTs?
The reason a GET was performed is because you did not specify a method, it
defaults to GET. It is always safest to do a POST.
In article [EMAIL PROTECTED], Brian Cassidy wrote:
I was working on a CGI::App, when it dawned on me that it's a little
silly that I have to explicitly declare an AUTOLOAD runmode. It irks me
a little because it's not really one of my VALID run modes, but
declaring it with $self-run_modes()
Andy,
I structure my templates like:
/[projectdir]/templates/modulename/*.tmpl
/[projectdir]/templates/modulename2/*.tmpl
Each module has a $modulename variable in it, so that load_tmpl()
automatically knows which directory to use when looking for templates.
Taking this a step further, I also
