Hi David
The first request will be rendered and then, depending on cache
configuration, cached accordingly.
Subsequent image requests are served from cache.
In addition, the rendering process is not as expensive as you might
imagine. The difference is that there is some processing (rendering)
done to scale the image, but streaming is same.
However, what you might also consider:
a) You need only one image (so less work from the creative side)
b) Storing only one image compared to store many images
The Web server (or front end cache) will look exactly the same, no
matter if you have one image which is scaled dynamically or you have
many pre-scaled images. At some stage they are all cached.
The real challenge here is to write a image scaling servlet which
renders photoshop quality images!
Cheers
Giancarlo
On Dec 2, 2008, at 1:21 PM, David Smith wrote:
Speaking from the peanut gallery, I would prefer the images be
pre-scaled and stored multiple ways in the DMS myself as it speeds up
rendering to the public. Scaling on the fly from a single copy to
each
client is expensive on system resources.
--David
Jackson Nicolas wrote:
Hi Ole,
You seem to be receiving a lot of responses but there's one I would
hope to read but isn't here. I was expecting that the "Magnolia-way"
would be not store multiple instances of the same image, but instead
one instance and be able to deliver multiple instances on request. In
this case, you would not have to make any changes to the DMS but
instead create a simple servlet that can deliver varying instances.
Unless you REALLY do have a valid reason to store multiple instances
of the same image, I don't see why you should. Since you want to do
the resize on automatically on the upload anyway, why not do it on
the
download. Magnolia is great with caching so you will only have to
resize once just as you would with the upload.
I hope this helps.
Best,
Jackson
On Tue, Dec 2, 2008 at 11:35 AM, Ole Christian Rynning <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I am currently in a very early stage evaluating Magnolia.
I need to import and manage several thousands of product images
with the WCMS/DMS. Typically the images are large jpgs, pngs, gifs
and pdfs. When importing I wish to automatically resize the image
into three sizes: thumbnail, product and large (+ full).
For this I wish to to develop a module/template that:
A) Automatically resizes the images and stores them into the DMS
i.e. under images/products/name-{thumb,small,large,full} upon
upload/import.
B) A template that allows the editor to navigate the DMS by
thumbnails, and insert images with selected size.
Can anybody give me some general pointers for how to do this (the
magnolia-way!)?
Best regards,
Ole Christian
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
----------------------------------------------------------------
