> The latter requires so much overhead (and serialization) that any benefit
> derived from Option A (entity caching in the container) is lost.
>
> jim
>

On what information do you base this statement ? Is this just anecdotal;
concrete studies with data would be most instructive.

If this is truly the case then there seem to be a lot of vendors out there
wasting someone's money selling & building shared caching technology.

If you are in a legacy data scenario where it is hard to tell when source
data has changed, I can see definite tradeoff that may zero each other out,
but there are many situations where clusters with replicated entity data
caching should be a realistic objective ..... or don't you agree ?

Thanks,
Matthew

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

Reply via email to