Re^3: RFC: Apache::Controller

or for an action to have more than one resulting template.
I'm not so sure about this. I would either make the template flexible enough to handle everything the action needs, or to create two different actions

But how do you know what action is going to get run, then?

See my example about form validation above. Basically, you recieve data from "form 1" ( to an action) , and you want to either a) go back to a form 1. b) proceed to form 2, and try to submit that (repeat for form 2, 3 etc.).

In your system you will need to include form 1 and form 2 into one template just because the action can't choose the template for you. It's certainly possible to do that, but I think it will get ugly very quickly.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^3: RFC: Apache::Controller

Replies are listed 'Best First'.
Re^4: RFC: Apache::Controller by revdiablo (Prior) on Dec 03, 2004 at 19:16 UTC
Basically, you recieve data from "form 1" ( to an action) , and you want to either a) go back to a form 1. b) proceed to form 2, and try to submit that (repeat for form 2, 3 etc.). I would make Form 1 and Form 2 two separate actions. Form 1 would submit to itself. If stuff was missing, it would return parameters that let the Form 1 template give an appropriate error message. If everything was fine, it would redirect to Form 2.	[reply]

Replies are listed 'Best First'.

Re^4: RFC: Apache::Controller
by revdiablo (Prior) on Dec 03, 2004 at 19:16 UTC

Basically, you recieve data from "form 1" ( to an action) , and you want to either a) go back to a form 1. b) proceed to form 2, and try to submit that (repeat for form 2, 3 etc.).

I would make Form 1 and Form 2 two separate actions. Form 1 would submit to itself. If stuff was missing, it would return parameters that let the Form 1 template give an appropriate error message. If everything was fine, it would redirect to Form 2.

[reply]