I haven't seen this particular solution here; what do people think of this: instead of having local and remote versions of Data, there are local and remote versions of high-level calls (such as "Reserve seat"), which query its own member Data object (which is always local). This way less data travels over the network, less computation happens on the client, and GUI is separate from business logic which is in turn separate from db implementation.
posted 14 years ago
...Data object (which is always local).
I meant, of course, local to the described object -- which, in turn, can be either local or remote.