We love Uploadify and we've never come up against a limitation that we haven't been able to work around.
That being said, and with all respect for your goal of keeping Uploadify lean, we would absolutely love to have client side resizing incorporated into an upcoming release.
It's saddens us to watch usertesting.com videos where people are sitting there with their 3MP upload slowly ticking-up, only to have to resize it as soon as it gets to our servers. So much wasted bandwidth!
But that would require admin permissions to cleints computers which a lot of ppl or virus software will shut down, it could be done with java or .net or flash/air maybe but all would be massive security risks. If you want to save bandwidth write a tutorial on how the customer can shrink or optimize the photo themselves before uploading and put a size limit on the uploads.
Personally Hello. I did a test with agile uploader. It resizes images client-side and forward. It is very good, it took four minutes pictures to send to the server now takes 10 seconds, not to mention that when PHP was trying to resize large images on the server it crashed. And without that usario have to understand image resizing and losing time for that. The only prolema thought that i could not run two instance idepen teeth within the same form, so I still think that if uploadify could do that he would be the maximum.
Actually, a resizing of the images on the client side would be all good.
It very much depends on what you are trying to do. Client side image sizing will, most likely, trim down the actual files leaving less to push.
On the other hand, client-side does not address the other burning issue – how to construct multiple sizes on the server end. And if multiple sizes on the server end is desirable then chopping off all that resolution before may not seem like a good idea.