Sorry, but I don't see the benefit. Since this is FormUI, we already know the names of the fields we're looking for. In fact, there's absolutely no reason you should ever have to access the raw $_POST data for a FormUI form.
That's why I'd prefer a random string. FormUI knows what its looking for, but it makes the form less vulnerable to sniffing/attack/mistakes. On Aug 16, 2009, at 8:59 AM, Caius Durling wrote: > > On 16 Aug 2009, at 13:23, Arthus Erea wrote: > >> Do you mean for the ID or for the name? >> >> I see no reason for the name. However, I think the name shouldn't >> actually be human-readable at all. It should be an encoded string >> (isn't it usually already?), so we are always sure the data is coming >> directly from the specific FormUI field. > > > For the name, so the field looks something like <input type="text" > name="comment[name]" id="comment_name"> > > Its not really to make the source code more human readable, but to > encapsulate the data in the $_POST more, so its split into named > arrays for each form. I find doing so makes it easy to select only the > bits of $_POST you need, without having to manually specify the fields > to use. > > C > --- > Caius Durling > [email protected] > +44 (0) 7960 268 100 > http://caius.name/ > > > > --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
