Emc Corporation

Open Text Corporation

Salesforce Com, Inc.

Box Limited

Venkat Chandrasekaran

Victor Spivak

Shu-Shang Sam Wei

Meir Amiel

Roger W Kilday

Yik-Ping Li

Xiaofeng Ma

David Buccola

Xiaodan Wang

Mikhail Chainani

Razmik Abnous

Utsavi Benani

Vikram Sardesai

William Dumaresq

Jia Chen

Tamar Bercovici

Vijay Devadhar

Roger Huang

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 is shared by one or more other instances of the lightweight type.

System for lightweight objects

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 is shareable by one or more other instances of the lightweight type.

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. One or more instances of the lightweight type share the instance of the sharable type.

A system may identify gap events in a change detection stream. When changes in data are transmitted to a downstream system, the system may identify intermittent portions of the transmission where data is missing (e.g., a gap event). In some examples, a gap event may be caused by system maintenance or one or more system errors. After identifying the gap event, the system may bridge the gap event using metadata associated with the gap event. The associated metadata may be transmitted (e.g., via a gap event identification message) to the downstream system, which may prevent the downstream system from experiencing computational inefficiencies due to the gap event.

Processing gap events in a change detection management system

Embodiments regard security descriptors for record access queries. An embodiment of a method includes: receiving a record access query, the query regarding records for a certain one or more users at a certain access level; searching one or more sharing tables of entities in a computing environment for security descriptors, each security descriptor being associated with a set of one or more users having access to one or more records of a set of records at an access level; identifying any security descriptors in the one or more sharing tables that relate to the certain one or more users with at least the certain access level; and searching the one or more records associated with each of the identified security descriptors according to the record access query.

Security descriptors for record access queries

Systems for managing shared content in a cloud-based service platform. A method commences upon identifying one or more storage devices that store one or more content objects. The storage devices may be partitioned into geographically distant locations. A first partition in one geography is associated with a first set of content objects and a second partition is associated with a second set of content objects. An inviter-collaborator generates a set of outgoing collaboration attributes pertaining to a shared content object from the first partition. The outgoing collaboration attributes are stored on the inviter's partition. An invitee-collaborator accepts the invitation and generates a set of incoming collaboration attributes that derive from the set of outgoing collaboration attributes. The set of incoming collaboration attributes are stored on the invitee's partition. The invitations can be sent and received through operation of a web application that facilitates offering invitations and acceptance of those invitations.

Accessing shared content using collaboration attribute partitioning

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.

Embodiments regard security descriptors for record access queries. An embodiment of a method includes: receiving a record access query, the query regarding records for a certain one or more users, groups, or both at a certain access level; searching one or more sharing tables of entities in a computing environment for security descriptors, each security descriptor being associated with a set of one or more users, groups, or both having access to one or more records of a set of records at an access level; identifying any security descriptors in the one or more sharing tables that relate to the certain one or more users, groups, or both with at least the certain access level; and searching the one or more records associated with each of the identified security descriptors according to the record access query.

Processing an object that shares a parent with another object is disclosed. An indication is received with respect to an object that shares a parent object instance with one or more other objects that a change associated with the object is to be made to a data comprising the shared parent object instance. The parent object instance is cloned to create a new parent object instance. The new parent object instance is designated as the parent of the object instance.

Conversion of lightweight object to a heavyweight object

Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes includes a plurality of attribute values associated with an object and is stored in a single database field that is not specific to any one attribute in the combined set of attributes.

Efficient storage of non-searchable attributes

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.

Retrieval of searchable and non-searchable attributes

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.

Optimized fetching for customization object attributes

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.

Growing community of inventors

Newark, CA, United States of America

Venkat Chandrasekaran