Hi Raghinii,
Thank you very much for your advice. The project which I plan to do is very
similar to web 2.0 picture sharing sites. The picture size may be big or small,
depending on user's uploading. At this situation, should I separately save
image contents into two database columns (small
If you want the best performance, I would do as you already mentioned and save
both the image thumbnail and the full size image in separate database columns
(separate records would be even better).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042722#4042722
Also, if you do use s:graphicImage, then you should use the fileName attribute
s:graphicImage fileName=icon-#{icon.id}-thumb / to allow the browser to
cache the image
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042753#4042753
Reply to the post :
Hi Shane and Peter,
Thank you so much for your great help. I really want to use Seam to build
an enterprise Web 2.0 site to demonstrate the great Seam framework. anonymous
wrote : save both the image thumbnail and the full size image in separate
database columns (separate records would be
I really depends on your read/write ratio and how often a given picture is
going to be displayed.
If you have a very large number of images where each image viewed only rarely,
even in its thumbnail form, then it might make sense to do it on the fly.
Resizing on the fly every time is
