brotherhood_of_LAN - 1:33 pm on Apr 28, 2013 (gmt 0)
It seems the discussion covers
1. # of files in a folder
2. Resizing/optimizing images client-side before upload
3. 1. Creating smaller versions of the same image after uploading on the server side OR 2. just serving the large image and letting the browser resize to the desired size OR 3. resizing the image using server side scripting, on every request.
For 1. It would depend on the filesystem but I would guess anything less than 100K folder/files isn't a big issue.
2. I use plupload and yes it seems to make sense to get clients to use their resources & save network transfer
3. I definitely wouldn't serve a larger image and let the browser resize it. Consider a 1MB image... and 50 concurrent users. You're going to need a 100Mb connection to serve them in a decent timeframe. Resizing them server side on *every* request just doesn't make sense.
IMO the point of having smaller images is that you do it once (even client side if you will), but it will be served more than once, so it makes sense to do it.