generally. no its not.. IMHO its a good thing it can help make data
validation easier, as in people can't fake variables by passing them in
the URL to the processing script.
It also helps keeps thing tidy... so providing that the processing isn't
fantastically complex (in which case the
hello everyone, is it 'bad form' (no pun intended) to have a form point to
itself for processing, rather than forward the form variables to another
page? Anybody have any input on this? I try to have 1 page that is the
form and handles all the processing as well in order to keep the page count
]
To: motorpsychkill [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2001 6:39 AM
Subject: Re: [PHP] bad form...
generally. no its not.. IMHO its a good thing it can help make data
validation easier, as in people can't fake variables by passing them in
the URL to the processing
No, that's alright,
as long as you design it to switch properly, like if($HTTP_(POST|GET)_VAR)
or whatever that assures you it is to be switched.
There's basically no difference if you use the same file or several instead.
Whatever suits you better.
I do it all the time.
Sincerely,
Maxim
Subject: Re: [PHP] bad form...
generally. no its not.. IMHO its a good thing it can help make data
validation easier, as in people can't fake variables by passing them in
the URL to the processing script.
It also helps keeps thing tidy... so providing that the processing isn't
fantastically
-
From: Tom Carter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 6:40 AM
To: motorpsychkill
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] bad form...
generally. no its not.. IMHO its a good thing it can help make data
validation easier, as in people can't fake variables
Dallas K. wrote:
On a previous shopping cart, some of our fantastically complex
scripts got so big that WE couldn't follow the logic too many
conditional test, things started to conflict it was hell... so we
found that it was better to break the processing code apart from the
7 matches
Mail list logo
