dtertman
Jul 16th, 2007, 03:19 PM
Page 1 of my site is a login form - user name, password. With the mass of documentation and examples, I had thought I could use SimpleFormController for this fairly easily.
Page 2 of my site (the success page) is another form. It needs data populated from business logic on initial display. This, it would seem to me, is another good use of SimpleFormController.
The problem/confusion I'm having is these two forms are sequential.
I don't want the data acquisition logic for Page 2 in the login page (very unmodular design), and I don't want the login processing in Page 2's controller (likewise). The examples I've seen use a RedirectView in this scenario - I (or rather my IS department) don't like that either - "too chatty" to have the unnecessary GET request just to get to page 2.
I would like to have the 2 separate pages/forms have 2 separate controllers, and have to success view from page 1 load up the formBacking / initial retrieval of page 2, but without going back to the client first. Possible?
Thanks!
Page 2 of my site (the success page) is another form. It needs data populated from business logic on initial display. This, it would seem to me, is another good use of SimpleFormController.
The problem/confusion I'm having is these two forms are sequential.
I don't want the data acquisition logic for Page 2 in the login page (very unmodular design), and I don't want the login processing in Page 2's controller (likewise). The examples I've seen use a RedirectView in this scenario - I (or rather my IS department) don't like that either - "too chatty" to have the unnecessary GET request just to get to page 2.
I would like to have the 2 separate pages/forms have 2 separate controllers, and have to success view from page 1 load up the formBacking / initial retrieval of page 2, but without going back to the client first. Possible?
Thanks!