If you cache in the oracle you still need a connection to it to get the data when running Java. Please remember that I want to ask if we can use EJB replacing the pure Java object caching...
-----Original Message----- From: Jose Ramon Diaz [mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 10:12 AM To: 'Struts Users Mailing List' Subject: RE: caching data in application server and EJB usage And why donīt you cache it in Oracle? Isnīt it enough? > -----Mensaje original----- > De: Zhang, Larry (L.) [mailto:[EMAIL PROTECTED] > Enviado el: lunes, 07 de junio de 2004 15:54 > Para: Struts Users Mailing List > Asunto: caching data in application server and EJB usage > > > I have a Oracle table that contains more than 10000 rows and > this table is almost a read-only table -- meaning that our > web application uses this table just for read purposes. Since > accessing the data in this table is frequent, so we decided > to do some sort of caching so that the performance is meet. > We cache the data from this table to application server's > memory. My question is that in this case can we use EJB > somehow to achieve the same goal? We select this because > caching the data in the memory is memory expensive and our > system has some memory constraints. > > Can you also discuss the pros and cons of using EJB and pure > Java object caching (of data to application server). > > Thanks for your answers. > > Larry Zhang > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
