The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The Business Delegate on encountering a business service failure, may implement automatic recovery features without exposing the problem to the client. If the recovery succeeds, the client need not know about the failure. If the recovery attempt does not succeed, then the Business Delegate needs to inform the client of the failure. Additionally, the business delegate methods may be synchronized, if necessary.
Measure twice cut once carpenter theory <br /> <br />Baiju <br />SCJCP, SCBCD, IBM-486, IBM-484, SCEA Part I
I guess you'd sychronize only if you were concerned about two threads competing for access of some shared resource. The design of your business delegate will tell you if it has any such sensitive resources, like a member variable holding information about the current call. Even so, it would often be better to synchronize smaller blocks of code on the resource than whole methods on the delegate. I'm using a vendor framework with proprietary business delegate thingies and there's nothing synchronized in them.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Onion rings are vegetable donuts. Taste this tiny ad: