Hi Lisa
One of the techniques I use is to let the client contain muliple proxy
objects. So for example if a person object is given to the client with just
a name and surname it will contain proxy objects to get diffrent groups of
data. So if the client chooses to look at his personal details there is a
proxy that contains that group of data and will be loaded on the client.
Or if the client chooses to view his banking history another proxy object
will be used to load that group of data. But also with this you may need to
use some form of cacheing depending on the use of the data.
Ahmed Chicktay
FutureJ - A Software Futures Company
> -----Original Message-----
> From: Lisa Retief [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 02, 1999 1:20 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Suggestions for implementing "lazy loading"
>
>
> Hi,
>
> I am trying to come up with and elegant way to share high-level objects
> between server and clients (in a multi-tier environment), but without
> creating unnessary network traffic. For example, the server may pass a
> Person object to the client, but containing just the bare minimum in terms
> of data. The client could then assess what further information it
> needs, tag
> these data structures somehow, and then ask the object to retrieve them.
> Obviously one would want to minimise server calls, but as trasparently as
> possible. I am calling this "lazy loading". These high level objects will
> probably take the form of Entity Java Beans.
>
> Does anyone have any experience, suggestions or patterns regarding an
> elegant implementation of this?
>
> Thanks in advance, Lisa
>
===========================================================================
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".
