Optional, esp. if the data is read only. The synchronization available in the Collections framework is there to avoid dirty reads. That collides with the caching. So it really depends on the caching policies, and the transactionality of the data in question.
Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: Dash Sam [mailto:[EMAIL PROTECTED]] > Sent: Sunday, November 17, 2002 4:14 PM > To: Juan Pablo Lorandi > Subject: Re: entity beans: concepts > > > > --- Juan Pablo Lorandi <[EMAIL PROTECTED]> wrote: > > Pedro, here's another solution to those spoken of already. > > > > Code your persistence as CMP Entity Beans(for simplicity). Create > > Value Objects ... > > [ ... snip ... ] > > No synchronization?? > > -- Sam > > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com =========================================================================== 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".
