Thanks Jamey, glad I'm not far off. With regard to action names, I can see what you mean but I think you've missed a step out of my process. I was thinking:
index: renders textbox to enter zip code and submits to 'new' new: looks up zipcode and renders select box of addresses at zipcode, user makes selection and form submits to 'create' create: redirect to the customer controller's 'new' action, passing unqiue reference to selected address I think we're more or less saying the same thing though. Andrew. On Jan 21, 3:09 pm, Jamey Cribbs <[email protected]> wrote: > On Thu, Jan 21, 2010 at 9:33 AM, Andrew Edwards > > Also, I would probably rename the NewCustomerAddress resource to > something like CustomerAddressZip or ZipCodeSearch. > > Other than that I think you are on the right track. The main point is > to not try to shoe-horn in all your actions into one controller. Keep > each controller to the basic seven. When you find yourself needing > more actions, it is time to create a new controller. > > Jamey
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
