Hi,
We have been working with the JSP taglib recently and have noticed that it lacks performance. It seems that Domino sessions are not pooled (bring one up at the start of the JSP and tear it down at the end) which makes the response times horrible. So i started to browse around and came across some WAS portal redbook where they mention something about a new “duration” attribute to the session-tag.
Is this applicable on the ordinary taglib as well (the redbook described how to use a “DominoSessionManager” to store a session in the HttpSession in the Login() method and remove it in the Logout()).
Say for example that you have an open WAS/Domino site with anonymous users. Are there any ways to get session pooling in this context. How would you terminate the domino session (and when?) if you don’t have any natural means to “exit” the users session. There is a time-out but without recycling the objects you will be in big trouble.
For the hell of it (and as a comparison) i built my own session pooling mechanism (with built-in time out/clean up, etc) in combination with a servlet and form-beans/view-beans. This way, i got sub-second response times, but it also meant a lot of more work. The JSP lib on the other hand is extremely powerful and rich but it lacks performance.
Will IBM ever implement some mechanisms to boost performance in this context? Or does such a mechanism exist today?
Kind regards
Daniel