Abstract: Updating an implementation object is disclosed. A proxy is configured to provide access to a first implementation object that is used to manage an item of content included in a collection of managed content. The first implementation object is replaced with a second implementation object. The proxy is associated with the second implementation object.

Abstract: Updating an implementation object is disclosed. A proxy is configured to provide access to a first implementation object that is used to manage an item of content included in a collection of managed content. The first implementation object is replaced with a second implementation object. The proxy is associated with the second implementation object.

Abstract: Batching content management operations to facilitate efficient database interactions is disclosed. Two or more content management-related requests are received. The two or more content management-related requests are treated as a batch, including by formulating and sending to a database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records.

Abstract: Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group.

Abstract: Preventing a resource leak is disclosed. An indication that an implementation object is no longer referenced by a user of the implementation object is received. The implementation object is prevented from becoming unavailable until after it is determined whether a resource associated with the implementation object is released.

Abstract: Batching content management operations to facilitate efficient database interactions is disclosed. Two or more content management-related requests are received. The two or more content management-related requests are treated as a batch, including by formulating and sending to a database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records.

Abstract: Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group.

Abstract: Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group.

Abstract: Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type may be shared by one or more other instances of the lightweight type.

Abstract: Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type may be shared by one or more other instances of the lightweight type.

Abstract: Converting heavyweight instances to lightweight instances is disclosed. An indication is received to convert one or more heavyweight instances to corresponding one or more lightweight instances. One or more sharable parent instances is/are created. One or more lightweight instances is/are created. For each lightweight instance, one of the one or more sharable parent instances is/are designated as a parent to create a lightweight composite instance. Each of at least a subset of the one or more sharable parent instances is shared by two or more lightweight instances. And, the created lightweight composite instances are configured to provide the functionality provided by the one or more heavyweight instances.