Yes. It is "authorized to act on behalf of" the client, in this case an Action. The Action _could_ do the whole job by itself. Nobody claims otherwise. But separating the "business function" from the Action, which is technically tied to the presentation, reduces coupling between the presentation and business tiers by hiding implementation details including infrastructure exceptions. It enables the reuse of the business logic within and across applications and presentation technologies. Changes are easier to manage because they are centralized. The delegate may provide caching services (thus better performance) for common service requests. And it hides the gory details of remote invocations when used in a distributed environment.
Jim > -----Original Message----- > From: Adam Hardy [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 12, 2002 3:15 PM > To: [EMAIL PROTECTED] > Subject: RE: What do you call them beans? > > > On Tue, 12 March 2002, "Cakalic, James" wrote: > > These Business Objects are what I referred to before as > "Business Delegates" > > or "Command Beans". Really, as I see it, you want your > Actions to be the > > transformation point between your presentation (using JSPs, HTML, > > ActionForms, etc.) and your model. This is responsibility > enough I think. > > > The Actions are the Controller part of the MVC, right? The > Controller part of MVC is new to me since I've been doing Java. > > The Microsoft n-tier approach pretty much ignores this facet > of an application. Sure you've got seperation of > presentation, business & data layers, but nothing addresses > the whole flow of control issue. > > Anyway, from what you say, do I assume the business objects > are called "delegates" because the controller delegates work to them? > > > Find the best deals on the web at AltaVista Shopping! > http://www.shopping.altavista.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> <font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
