Caching is usually handled by the database tools. In JetSpeed's case that's torque, so yes the connections are cached. Within the torque config file you can specify how many connections it should cheap open and the max connections.
On Wednesday 03 March 2004 09:56 am, Nikolaos Athanasis wrote: > Hi all, > > I am working with jetspeed 1.4. under tomcat 4.1.29. > > My application consists of several JspPortlets. One of them, every time a > user clicks in a hyperlink of another portlet, connects to a database, > makes a query, transforms the query result with XSLT (the query result is > in XML/RDF format) and shows the content in html. > > I ascertain that if a user fires this hyperlink twice, then the execution > time of the query is much less. Is it possilble that this is because of > caching in jetspeed? > > Before answering, you can check it online: > http://139.91.183.233:1025/jetspeed/index.jsp > > just click "Artist" from the left, and then click "Get Resources". > If you click "Get Resources" twice, is it possible that the content is > served from the cache? > > Thank you! > Nik... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
