Abstract: A method for providing local access to managed content is disclosed. The method comprises receiving from a remote host a request to perform an operation with respect to content associated with a set of managed content and obtaining information required to respond to the request. The method further comprises providing in response to the request a content locator usable to perform the requested operation through direct communication with a local content system associated with the remote host.

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: A method for providing direct access to distributed managed content is disclosed. The method comprises receiving a request to perform an operation with respect to content associated with a set of managed content and obtaining information required to respond to the request. The method further comprises providing in response to the request one or more content locators, each content locator being usable to perform the requested operation through direct communication with an associated one of a plurality of content systems used to store at a portion of the distributed managed content.

Abstract: Receiving and executing at a server a script provided by a client, e.g., in a service request sent by a web services or other service client and/or consumer, is disclosed. In various embodiments, the script is configured to cause the server to do one or more of the following: pre-process at least a portion of the services request; post-process a response data associated with the services request; and replace an operation comprising the service at least in part with a replacement operation defined or identified at least in part in the script.

Abstract: Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes.

Abstract: Federated search is disclosed. A result associated with a search of a content source not natively configured to provide content type data for content items is received. A content type is associated with a content item included in the result based at least in part on information associated with the result.

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: Smart containers are disclosed. A system for managing content comprises an interface to receive an operation associated with an instance of a smart container. The smart container comprises a logical structure configure using a definition to manage associated content. The system for managing content comprises a processor configured to determine whether the operation is allowable based at least in part on a policy; and in the event that the operation is allowable, perform the operation. A memory is coupled to the processor and is configured to provide the processor with instructions.

Abstract: Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

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: Federated search is disclosed. A result associated with a search of a content source not natively configured to provide content type data for content items is received. A content type is associated with a content item included in the result based at least in part on information associated with the result.

Abstract: Deploying and distributing content management code is disclosed. A software object class is received at a repository. The software object class is stored at the repository. The software object class is downloaded from the repository to an application server associated with the repository.

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: An attribute is received for storage. Whether the attribute is searchable or non-searchable in storage is determined. Storing the attribute as a searchable attribute comprises storing the attribute in a database table corresponding to a hierarchical class-based object. Storing the attribute as a non-searchable attribute comprises storing the attribute together with one or more other non-searchable attributes as a set of attributes. The set of attributes is stored in a database location outside the database table corresponding to the hierarchical class-based object, and the database location is accessed before the database table. A unique attribute identifier is associated with the attribute to distinguish between a name of the attribute and a name of one of the one or more other non-searchable attributes in the event that the name of the attribute and the name of the one of the one or more other non-searchable attributes are assigned the same name.

Abstract: Smart containers are disclosed. A definition is received of a logical structure configured to manage associated content. A policy or operation specified by the definition is applied to an item of content associated with an instance of the logical structure.

Abstract: Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set.

Abstract: Managing stored content is disclosed. It is determined that a new or modified attribute is to be associated with future-created instances of an object type but not with at least some previously-created instances of the object type. A default intra-type customization that associates the new or modified attribute with future-created instances of the object type, in a manner that results in the new or modified attribute being stored in a database structure that is separate from a type-specific structure configured to store one or more type-based attributes common to both the at least some previously-created and future-created instances of the object type, is associated with the object type.

Abstract: An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level.