| Just wondering how you guys would approach this pretty standard task. I've been jumping around frameworks, and am constantly surprised with the pitfalls each one has at doing something so common. I'm not asking you guys to write anything -- just brainstorm about whether it's currently pheasible, whether libraries exist, if anything would be particularly troubling, etc. Task:
Make an image gallery where users may log in via OpenID and upload files. Persistent information should be stored in a database, and uploaded files placed on the hard disk. All images should be sized down to a particular maximum size, and flickr style thumbnails should be generated for the gallery view. It should be possible to comment on the images, and the original uploader should be able to change the file without dissociating these comments. Also, users should be able to upload a small (automatically downsized) image to use as their personal icon. Possible Pitfalls and Considerations:
How do we tell if the file is not an image? What do you do then?
What if the file is really big, and eats up our bandwidth / disk space?
Do we have any support for truly temporary files? We wouldn't want one user's file to upload over another, when we're still trying to shrink and process it.
How do we avoid orphaning images if users re-upload things?
Should user icons be considered the same sort of thing as gallery images?
Should we store anything relating to the images in our database at all? |
