Again, source code licensees can choose to remove this new feature from their compile and to continue to use the existing message-oriented send functions. But developers will not need to write custom code to distribute object state unless they want to. This release includes a robust set of default view implementations supporting duplicated objects. By using these default constructs, developers can easily designate which parts of an object should be distributed and under what conditions. The default components will automatically generate the proper views to distribute the state.
Distribution occurs transparently to the object.
It can reference and use a member-distributed variable just like any other variable, and changes to state will be automatically propagated to any duplicates of the object on all clients. The object does not need to know whether it is the original object or a duplicate receiving an update. In previous releases, only the LTObject component of an object was automatically created on the client in this circumstance. In this release, the new implementation relieves developers of the burden of writing special code to bind the client-side LTObject to a custom class. Source code licensees can easily override this default implementation with one of their own if they find it to be inadequate or overkill for their specific needs.