Hi, Part of my site includes a gallery: various resizing / cropping code already exists in phpThumb (and I have used it before), and I would think some level of integration with phpThumb would be good. However, I have thought of a number of ways to do it, but I'm not sure of the best, especially with respect to caching:
Using the phpThumb caching: - Upload files and simply a have links in the page using the standard phpThumb syntax. phpThumb.php?src=../images/3.jpg<otheroptions>. The would use the phpThumb caching, but would not have 'nice friendly urls' (something I would prefer)... say '/images/my-picture-of- something.jpg' Using Agavi caching: - Use phpThumb as an object within an Agavi model. The view would call the model to get the image data. This could be done in two ways: - Store images in the database - Store images as files However, I'm not sure which way is best. In both ways I would like to set up caching for the 'showImage' action/ views. Looking at http://groups.google.com/group/agavi-users/browse_thread/thread/b40538716e2bbc3c/b0d99ff5f0b918f7?lnk=gst&q=cache#b0d99ff5f0b918f7 , I think I could do it. However, there is the issue of 'other options' passed to phpThumb: say certain size or quality constraints which, while typically would not change, I would like to 'cache against', but I'm not sure how to do that. What do people think? At the moment I think I'm more pro saving the images as files, and not in the database, and using Agavi caching. Before I set off trying to do it, I do wonder if there are any issues with this that I've not thought of...? Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
