Thanks to Rickard for his analysis of Roger's article.
Roger's contention that EJB Entity and Stateful Session components are
not efficient enough for enterprise use and the 'analysis' that supports
that contention unfortunately has no basis in fact.
The major overhead in most components is the database lookup and update.
MTS components don't provide any optimization of this function. They are
just harder to program because developers are forced to use stateless
functions. The EJB entity model does not require any extra database
overhead and since the EJB container understands what the developer is
trying to achieve it can help optimize the work.
I'm not an expert in COM or COM+ but it is my impression that there is
no simple way to cache the database data for a business component even
across multiple method calls within the same transaction. With EJB, both
Entities and Sessions get this for free (from the developers
perspective). In the multi-method per transaction scenario I would
expect MTS objects to make many more database requests than the
equivalent EJB components.
If Roger were more observant he would see that the current MTS 'object'
model is woefully outdated and is based on assumptions about
'efficiency' that might have been true in the '70s but are no longer
considered relevant by the industry.
-- Mark
===========================================================================
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".
