You are able to store the object to a file, or some other method of persistent storage. PSOM requires that all Persistent objects be derived from a Persistent class, and the Persistent data must be explicitly spelled out. This is in contrast to DSOM, where a given object does not have to know in advance that it is going to be distributed. Once you derive your Persistent object from the SOMPersistentObject class, the rest is surprisingly straightforward. If you have multiple users sharing a Planner, any change one user makes to a Planner is not automatically reflected on other users' Planners.
Framework is designed to propagate an update to a given object to all other replicated objects.
Updates are propagated directly to the other objects, without the use of secondary storage. RSOM is the ideal Framework for groupware applications, such as real-time creation of compound documents, without the traditional bottleneck of a database server. In common with the PSOM Framework, RSOM objects are required to be RSOM-aware objects derived from the SOMRreplb class. After reviewing several important rules that replicated objects need to adhere to, Lau declares the Daily Planner applet complete. If you are programming to a single operating environment, RSOM's complete object-replication capability is ideal.