4 ms·

Thanks. It seemed to me in the beginning that HIDDEN fields were a very clumsy solution. Now I understand why they indeed are. We use PHP as our server side sc

by amrithk 18y ago

Thanks. It seemed to me in the beginning that HIDDEN fields were a very clumsy solution. Now I understand why they indeed are. We use PHP as our server side scripting language. I was thinking of using the $_SESSION variable but attributes and pointer information for 30 image uploads per user * no of concurrent users seems like a huge drag on server memory. I'll probably just write the pointer information to the database for now after each upload. It might make the web app slower by a few milliseconds but it reduces unnecessary complications

olefoo 18y ago
PHP uses files for storing sessions; you do want to restrict where on your site you are using sessions as they do have side-effects. Most notably any page served in a path configured for sessions will have an expiry time in the past and a bunch of no-cache headers; for a dynamic page that is the behaviour you want, make sure it's not being applied where it should not be.