POST data is not structured, so while you can use multiple forms on the same page, there could also be namespace conflicts. The resulting query string (in case of a conflict) could be really bizarre and prone to subtle bugs. Not a problem when it's you writing the code or when the page is stupid-simple. Problem if you are doing complicated stuff and others might inherit the code.
If you want to see how Amazon implemented their form, Firebug is your friend. I'm not trying to convince, just offer a possible explanation :) On Dec 9, 2008, at 9:26 AM, pepe wrote: > > I agree with Hassan. If you want to give your pages multiple > functionality you have to be able to use multiple forms. Just look at > Amazon, for example. After you have chosen a book/other and it's in > your cart you have a form to check out but they also offer selecting > more items. Are both things one and the same or are they run by the > same form? I hardly think so. > > Pepe > > On Dec 8, 11:17 am, "Hassan Schroeder" <[EMAIL PROTECTED]> > wrote: >> On Mon, Dec 8, 2008 at 4:07 AM, Chirantan >> <[EMAIL PROTECTED]> wrote: >>> I have heard few people saying that >>> one must avoid using multiple forms on the same page but I never >>> got a >>> convincing explanation for the same. >> >> I've never heard that, and can't imagine why anyone would think it a >> problem. I've certainly had projects that required multiple forms >> per page. >> >> FWIW, >> -- >> Hassan Schroeder ------------------------ [EMAIL PROTECTED] > > --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
