Well - the `image.set(..)` would be in the servlet responsible for rendering the image (aka his servlet). Setting `image.set(...)` in the HTML script that writes out `<img src=".."/>` wouldnt do anything since its not responsible for rendering the image. (image rendition is on a totally diff request).

To provide transform params you can either read them from the data (normal way) or pass them on the wire (which is what @XiaohuiYang is doing)

I think the use case might be:

1. You have a Feature component that displays an image 300px wide to fit the sidebar.
2. 100 feature components are added to page sidebars.
3. Site design hits and sidebar expands to 360px

* If authors had set 300px via dialog on each component, each component resource would need to be updated
* If the component wrote width=300px on resource creation, each component resource would need to be update
* If `featured.jsp` contains `<img src="<%= resource.getPath() %>.img.300.0.png`/> then only the `feature.jsp` would need to be updated (to `.img.360.0.png`)
* You never have to touch the Servlet code and any number of components can be consumers of it to resize their images.

Unless *i'm* missing something :) -- I see where @XiaohuiYang is coming from, i'm just sure i'm sold on the impl.

.. Or we can just wait for @XiaohuiYang to wake up and sort this all out :P