Hi! How do you handle the following topics:
1) Lets say the DAO is involved in a transaction with a isolation level that means that data should not be visible to clients outside the transaction until the transaction is commit? The solution to this could be to let the cache implement XAResource and use transaction that span the jdbc calls and the calls to update the cache. 2) To decrease the impact on the heap space the cache could use a map that extends abstractmap and uses SoftReferences. Thanx Lars-Fredrik Smedberg Senior Architect, Mynta Management & IT AB -----Original Message----- From: Lawrence Bruhmuller [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 06, 2001 02:38 AM To: [EMAIL PROTECTED] Subject: New J2EE design pattern Hello all, I just wanted to call your attention to a new J2EE design pattern that I have posted on TheServerSide.com, dealing with strategies for caching business data and thereby speeding up your application. Please don't hesitate to provide any feedback (either to me directly or using the forum at TSS). http://www.theserverside.com/patterns/thread.jsp?thread_id=10610 Regards, Lawrence Bruhmuller =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
