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]
