I was curious if I would run into any problems storing binary data in session variables.
Here is the problem er rather challenge!:
I want to design a multi-part form which may include several steps before the final data is put together and stored in a database. I want the form to be able to get past some ISPs' requirement of accepting only a single upload at a time via the max simultaneous uploads directive in php.ini. Am I interpretting that correctly or can there be multiple files uploaded in a single HTTP request... is it per HTTP request or is it allowing only one file to upload at a time one after another? I've done some research on this and can't seem to even find a reference to how many uploads may occur at a time... maybe I just dreamed the whole thing up!
I was thinking if I could design a function to build hidden fields automatically between steps and store any files in $_SESSION variables then I may have this thing licked. I wanted to go with $_SESSION variables because then if a user inadvertently closes the browser or spontaneously stops in the middle of the submission process then whatever binary data would be destroyed with the other $_SESSION data no harm done, no files left to clean up off of the server. Then after a successful database insert, destroy the leftover binary data in the $_SESSION array with unset().
Just curious if I am going to run into any limitations or possible pitfalls with this solution. I'm thinking since most ISPs limit the size of uploaded files to 2MB, no file would be larger than that and in fact I would probably impose a 1MB limit.
: )
Rich
:::::::::::::::::::::::::::::::::
Smiling Souls
http://www.smilingsouls.net
:::::::::::::::::::::::::::::::::
Storing binary data in $_SESSION variables
