So far, using Telerik OpenAccess ORM has been presented in the context of a direct database connection. But there are also application situations that do not allow a direct or a permanent database connection. Examples are Web applications and other asynchronous applications that still need to deal directly with objects. Also consider handheld applications that are, for most of the time, disconnected from the primary object store but must intermittently synchronize with the database server. Or applications that need to serialize parts of the database for transmission to a remote application and reintegrate any changes made remotely.
It is possible to work without a database connection and still get all the benefits provided by the OpenAccess ORM framework. Complementing the IObjectScope interface for direct connections, Telerik OpenAccess ORM provides an ObjectContainer class for working with disconnected persistent class instances.