I'd go for the routing approach. While certainly both approaches are
working, directing the input to the proper action feels more like a
routing task to me. However, that breaks the "one url, one resource"
paradigm, but that's true for both approaches.
cheers
felix
On Nov 14, 2008, at 8:10 PM, David Zülke wrote:
I think both are valid approaches.
A proxy action as you describe it has the specific purpose of doing
this one thing for "multi-submit button forms", so it's no violation
of the MVC paradigm or anything.
In general, I guess I'd prefer that over the routing approach which
feels a tag hackier, as you said.
- David
Am 13.11.2008 um 09:59 schrieb Veikko Mäkinen:
Hey,
I have a simple HTML form with several submit buttons and I need to
trigger different action from all of them and all actions need to
receive form's POST data.
I'd like to ask how people here would deal with this. So far I have
two
possible solutions:
1. "Proxy action" which checks what button was clicked and forwards
to
the correct action.
2. Routing hack with _POST routing source (works pretty nicely, I
tried :)
Any comments on those or better solutions? All ideas will be greatly
appreciated.
-veikko
P.S. I'm developing an application that is also used with portable
devices that have zero support for Javascript techniques. This
limits my
options to standard HTML + Agavi awesomeness :)
--
Veikko Mäkinen
[EMAIL PROTECTED]
044 5910 413
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users