Re: Caching of read-only DB contents in an EJB

[Lahooti, Hamid]

Caching requires singleton capability that ejb does not currently offer.
You best (only) bet is to use CORBA/RMI server and delegate
the property read operations from your ejb to the cache server.
You will then have to worry about how to maintain the cache in sync
with the database.

>I'm currently working on my diploma thesis "Application Architectures >with
the J2EE". One of the issues I want to work on is about database >caching. A
question I'm currently facing is the following:
>For performance issues, one could try to cache records of a read-only
>database in an EJB. However, this might raise some new problems, some
>questions at least:
1. What type of EJB is is best suited for this job: Entity or Stateless
Session
(Stateful Session doesn't make sense, I think)?
>

===========================================================================
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".