🚀 go-pugleaf

One approach would be to make Person a serializible class, and make the
collection of children that Person holds a remote class.  Then, whenever a
Person gets serialized from server to client, the contents of the collection
won't be serialized, only its remote reference will be transferred.

The server implementation of the collection class could use lazy
initialization to defer doing any work (like querying a database) until the
client starts asking for children.  If the collection supports a method that
allows for many children to be requested at once, then just those children
that are needed at any given time can be serialized, avoiding repeated calls
over the network.

By the way, I'm having trouble finding information that discusses these
types of issues - if anyone out there knows of a good source of practical
information on "how to design distributed apps", I'd like to hear about it.

Vidur Dhanda wrote:

> I'm having some trouble fully understanding a design issue.  Perhaps,
> some reader can point out a design pattern or offer some insight.
> Please bear with me, I think I'm making it a lot harder than it need be.
>