Here is my 2cents
I will not use GET. If you want to pass a db name i would use POST. Because
if you don't do something with the statusbar the the user can see the dbname
if you use GET and i don't think that is a good thing. I'm working on an
webbased app with a lot of db work and i learnt "Don't trust the user" not
even if it is just the intranet.

There my 2cents
"Goltsios Theodore" <[EMAIL PROTECTED]> wrote in message
> I thought I just did a comment and suggested that it is a lame solution
> to use $_REQUEST plus I did not know witch of the two method  (POST or
> GET) would be appropriate so I picked up the lame way :-) .
> mike wrote:
> > On 8/24/07, Goltsios Theodore <[EMAIL PROTECTED]> wrote:
> >
> >> the posted or got option buy using the $_REQUEST array ($_GET and
$_POST are
> >> included in that like a less lame solution). Let's say you have a
> >>
> >
> > Please do not encourage the use of $_REQUEST.
> >
> > You might as well just tell people to enable register_globals again.
> >
> > Use $_GET, $_POST, $_SESSION, $_COOKIE, $_SERVER, etc. for the
> > appropriate source of data. $_REQUEST is laziness and introduces most
> > of the same issues that was the reasoning behind disabling
> > register_globals to begin with.
> >
> > (As for dropdowns, that's just an in-browser method of collecting data
> > and sending the key/value pairs in POST or GET... IMHO the HTML
> > portion should already be known before someone steps into the realm of
> > PHP and server-side programming)
> >
> > - mike
> >
> >

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to