Looking at MVC as it is implemented in, for instance, the Pet Shop example,
the communication between servlet and EJB looks kinda chatty. I mean, the
controller updates and then returns a list of models that need to be
updated and most of the models in return call out to the EJB tier for their
model data. Would it not be more efficient to return the populated models
via the update call? Are there any rules of thumb about :
1. the max size of an object to send to the mid-tier
2. the number of times that the client portion of the app calls the
mid-tier
3. proper use of return values from a session bean?
John
===========================================================================
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".
