"Lahooti, Hamid" wrote:
>
> That's easier said than done. LRU does not help you when a different
> container updates your bean instance's external representation. Pretty
> soon your cache is out of date!
>
Yes, if you have multiple JVMs running that's the case. But that doesn't mean
every container should throw away each instance as soon as the transaction is
completed. That means that either the same database should be used by all
running instances (not copies) and that the containers should load any data
needed if it suspects that it is inconsistent. If you want to load-balance on
every call, then you would passivate all the time, but in my opinion that's a
bad way to do load-balancing (and doesn't fit entity beans, session beans would
seem more adequate).
/Kalle
--
At a French Hotel: "A sports jacket may be worn to dinner, but no trouser."
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://travel.to/kp
Telephone: +46-(0)13-17 99 29
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
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".
