Currently AFAIK, when you use the Session storage
Storage object, every time an image is generated,
it is stored in the session.
When the same client asks for the same chart at an
interval, 2 ChartImage will be stored in the session.
If you have a lot of client, the session will be
overwhelmed with unused objects that will only be
destroyed on timeout.
So I added an boolean option in the img
tag "removeAfterDisplay" (defaults to true)
which send this request parameter to the renderer
servlet so that the renderer decides wether he should
remove the Object from the Storage or not.
In order to do that, I added the method
public ChartImage removeChartImage(String cid,
in the Storage interface and implemented it in the
Log in to post a comment.