Thanks Ken! I just put in your NOAA reports script the other day - love it.
I had that concern with the $argv . I think I concluded that allowing that array was something that needed to be told to turn on at the server(just guessing as it didn't work out of the box for me) and if so, it might be better off, being it seemed anything could be passed.
With the GET, it seemed a better idea (read as 'easier') but still allowing anything even with coding the file extension in the script. Your suggestion makes solid sense to me; giving a list of "OK parameters" that can be expanded when needed AND already knowing the outfile name while only running one script .
Right now, it just returns the "outfile" (a thumbnail) to a "<img src=" tag in the HTML. The filenames are not user inputted but rather part of the html code. The idea was to not update the "outfile" unless it was being looked at and to avoid doing them (all whopping 3 of them
...) all at once; trying to be efficient. The infile (fullsize jpeg) is always uploaded/updated but I figured, with the little traffic I have, it would reduce some overhead by only running the needed jpeg when needed.
Then, of course, I acknowledged that different pages might have different "outfile" thumbnails and wanted to reduce the typing/typos/simplify the usage. I think your suggestion hits it for me - thanks. I'll play with it tomorrow.
PHP is still a foggy learning process for these impatient old brain cells, as must be obvious, but I am having some fun with the simple stuff. BUT the ability for El Diablo to manipulate a scenerio because of open, passed parameters caused me to ask so I must be learning something...