In a J2EE application, the client will often interact directly with business components via RMI. There are a couple of negative consequences: RMI code is subject to change if the business components change, and the client must deal manually with caching resources (e.g. a stable list of business locations). Both of these complexities can be hidden behind a client-side business delegate layer. The components in this layer provide an API for client-side code, while encapsulating the RMI and caching code that can change as a result of changes in other business components.
posted 14 years ago
It sounds like you understand it to me... What's your question? Kyle