>Just an idea: could the file be temporarily stored in the session >instead? At least then it won't be sent "over the wire" multiple >times. Storing it in the session avoids having to introduce yet
Files can be big. Don't think that it's a good idea to either send it over the wire or store it in the DB. Some things are best stored in the filesystem, that's why they call it _file_system ;-) I would just store them in a configureable temp directory and add a cleaning routine that removes temp files whose ctime is older than some configured maximum of seconds. Maybe give them a directory structure to prevent too many files in one directory, too (for sites with heavy upload numbers). This might not be a perfect solution, but it's a practical solution. And sometimes practical is the best you can get. bye, Georg
