I was talking about the static resources, but in the end it is the same
discussion. Except for those dynamicly generated resource you might want
to additionally have some kind of cache (like memory or filesystem).
When such a resource is cached, the same inefficiency holds true as for
the static resources.
Eelco
Johan Compagner wrote:
i also thought that this discussion was also about dynamic images that
are generated once (per session or what ever)
And then saved to the work dir so that they can be cached (both sides)
as long as it is possible.
Or are we talking purely about static/fixed images in the jar of the
component..?
johan
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
