Abstract: An episodic execution of program instances and a coordinated message exchange protocol are combined to achieve eventual consistency in the communication between nodes of a distributed system. Program instances run in episodic loops that are triggered by defined input events and that generate checkpoints. The checkpoints indicate when messages are to be sent from the one instance to another instance or other device. The coordinated message exchange protocol allows the instance to send a message to a receiver, to acknowledge that the message has been received, and to confirm the acknowledgement to the receiver.

Abstract: Linking data items describing a person into a single, unified contact entry without merging the data items. The data items include, for example, contact data, social network data, and other data describing the person. The contact entry is a single representation of the person that, in some embodiments, combines a plurality of personas of the person without merging the underlying data items. Metadata representing one or more contact entries is capable of being shared across a plurality of devices and applications such that a user is presented with a consistent contact list on different devices and from within different applications. In some embodiments, the user annotates one or more of the contact entries with notes or other data that is stored with the metadata.

Abstract: Instance properties are defined for instances of an application. During episodes of the instances, the values of the instance properties are populated. Other instances read the values of the instance properties without requiring the instance to run. If the value of an instance property is not populated, then a new episode of the instance is executed to populate the missing values. Instance properties may be grouped into property bags. An instance may populate the values of instance properties in a property bag atomically during one episode using a multi-set message. Other instances may read the values of the property bag instance properties using a multi-get request.

Abstract: An episodic execution of program instances and a coordinated message exchange protocol are combined to achieve eventual consistency in the communication between nodes of a distributed system. Program instances run in episodic loops that are triggered by defined input events and that generate checkpoints. The checkpoints indicate when messages are to be sent from the one instance to another instance or other device. The coordinated message exchange protocol allows the instance to send a message to a receiver, to acknowledge that the message has been received, and to confirm the acknowledgement to the receiver.

Abstract: A hosted resource management system is described herein that provides systems and methods whereby a cloud-based tenant can define a logical model that allows the tenant to work with cloud-based entities in a manner that aligns with the tenant's own purpose and thinking. The system then reflects this model in a set of management tools and access paradigms that are provided to the cloud-based tenant. Each division in the logical model is termed a scope, and can include various types of cloud-based entities. Each of these scopes may contain similar cloud-based entity types, but because of the organization provided by scopes the tenant can manage these cloud-based entities according to the view and model that the tenant defines. Thus, the hosted resource management system provides a way of managing cloud-based entities that is intuitive for cloud-based tenants and facilities easier management of large-scale applications with many cloud-based entities.

Abstract: An episodic execution of program instances and a coordinated message exchange protocol are combined to achieve eventual consistency in the communication between nodes of a distributed system. Program instances run in episodic loops that are triggered by defined input events and that generate checkpoints. The checkpoints indicate when messages are to be sent from the one instance to another instance or other device. The coordinated message exchange protocol allows the instance to send a message to a receiver, to acknowledge that the message has been received, and to confirm the acknowledgement to the receiver.

Abstract: A distributed instance system manages instances and communications between the instances. The distributed instance system provides a restricted set of communication methods to the instances. Based on the type of communication method used, the distributed instance system has knowledge of the messages sent by instances and can make decisions on how to handle the messages. When one of the instances involved in a message exchange ends, the host uses its knowledge of the message exchange type to determine whether to drop the message, drop a reply to the message, and/or send an error message to the surviving instance. An instance may create one or more child instances in a tree-like configuration. Status data is passed up the tree from children instances and aggregated in the parent instances. Monitoring data may be generated from the aggregated status data.

Abstract: Architecture for a session lock and lobby feature in a distributed conferencing framework for a conferencing session. Under a lock scenario, once a user enters the session, the session can be locked to prevent other individuals from entering, even if the individuals were invited to the session. Locking can be accomplished manually by a session participant and/or automatically based on criteria. The lobby feature allows a session participant to be aware of users in the lobby and pending access to the session by providing notification and/or identification of the user attempting to gain access. The session leader can selectively allow access to the session. The architecture facilitates lock and lobby features in multiple identical, leaderless, conference servers which together form a distributed conferencing system. The lock and lobby features can employ media session protocols such as session initiation protocol (SIP) and centralized conference control protocol (C3P).

Abstract: A hosted resource management system is described herein that provides systems and methods whereby a cloud-based tenant can define a logical model that allows the tenant to work with cloud-based entities in a manner that aligns with the tenant's own purpose and thinking. The system then reflects this model in a set of management tools and access paradigms that are provided to the cloud-based tenant. Each division in the logical model is termed a scope, and can include various types of cloud-based entities. Each of these scopes may contain similar cloud-based entity types, but because of the organization provided by scopes the tenant can manage these cloud-based entities according to the view and model that the tenant defines. Thus, the hosted resource management system provides a way of managing cloud-based entities that is intuitive for cloud-based tenants and facilities easier management of large-scale applications with many cloud-based entities.

Abstract: Instance properties are defined for instances of an application. During episodes of the instances, the values of the instance properties are populated. Other instances read the values of the instance properties without requiring the instance to run. If the value of an instance property is not populated, then a new episode of the instance is executed to populate the missing values. Instance properties may be grouped into property bags. An instance may populate the values of instance properties in a property bag atomically during one episode using a multi-set message. Other instances may read the values of the property bag instance properties using a multi-get request.

Abstract: An episodic execution of program instances and a coordinated message exchange protocol are combined to achieve eventual consistency in the communication between nodes of a distributed system. Program instances run in episodic loops that are triggered by defined input events and that generate checkpoints. The checkpoints indicate when messages are to be sent from the one instance to another instance or other device. The coordinated message exchange protocol allows the instance to send a message to a receiver, to acknowledge that the message has been received, and to confirm the acknowledgement to the receiver.

Abstract: A distributed instance system manages instances and communications between the instances. The distributed instance system provides a restricted set of communication methods to the instances. Based on the type of communication method used, the distributed instance system has knowledge of the messages sent by instances and can make decisions on how to handle the messages. When one of the instances involved in a message exchange ends, the host uses its knowledge of the message exchange type to determine whether to drop the message, drop a reply to the message, and/or send an error message to the surviving instance. An instance may create one or more child instances in a tree-like configuration. Status data is passed up the tree from children instances and aggregated in the parent instances. Monitoring data may be generated from the aggregated status data.

Abstract: Architecture that facilitates management and control of sidebar sessions (or breakout rooms) in a distributed conferencing environment. Distributed frontends (or MCUs) are provided for multi-party access into a main conferencing session. In one implementation, the main session can then be partitioned to provide one or more sidebar sessions for side conferencing. The sidebar sessions can all be contained on a single MCU or distributed across multiple MCUs. The leader of the main session can then freely roam among the sidebar sessions of a single MCU or among the sessions on the distributed MCUs. The protocol can be SIP-based, and also or alternatively use C3P commands for creating (or adding) a sidebar session, modifying the sidebar, moving users to and from a sidebar, and deleting the sidebar session.

Abstract: Linking data items describing a person into a single, unified contact entry without merging the data items. The data items include, for example, contact data, social network data, and other data describing the person. The contact entry is a single representation of the person that, in some embodiments, combines a plurality of personas of the person without merging the underlying data items. Metadata representing one or more contact entries is capable of being shared across a plurality of devices and applications such that a user is presented with a consistent contact list on different devices and from within different applications. In some embodiments, the user annotates one or more of the contact entries with notes or other data that is stored with the metadata.

Abstract: A method for providing a low fidelity alternative until a high fidelity experience becomes available is provided. Upon detecting a need to download data, a download manager determines a download priority for downloading the data. The download priority specifies an amount of a low fidelity representation of data to download prior to downloading a high fidelity representation of the same data and any remaining low fidelity representation of the data simultaneously. The download manager then downloads, for example, from a content server, the low fidelity representation of the data and the high fidelity representation of the data according to the determined download priority, thus allowing the low fidelity representation of the data to be used until the high fidelity representation of the data is downloaded and becomes available.

Abstract: Architecture that facilitates management and control of sidebar sessions (or breakout rooms) in a distributed conferencing environment. Distributed frontends (or MCUs) are provided for multi-party access into a main conferencing session. In one implementation, the main session can then be partitioned to provide one or more sidebar sessions for side conferencing. The sidebar sessions can all be contained on a single MCU or distributed across multiple MCUs. The leader of the main session can then freely roam among the sidebar sessions of a single MCU or among the sessions on the distributed MCUs. The protocol can be SIP-based, and also or alternatively use C3P commands for creating (or adding) a sidebar session, modifying the sidebar, moving users to and from a sidebar, and deleting the sidebar session.

Abstract: Architecture for a session lock and lobby feature in a distributed conferencing framework for a conferencing session. Under a lock scenario, once a user enters the session, the session can be locked to prevent other individuals from entering, even if the individuals were invited to the session. Locking can be accomplished manually by a session participant and/or automatically based on criteria. The lobby feature allows a session participant to be aware of users in the lobby and pending access to the session by providing notification and/or identification of the user attempting to gain access to the session. The session leader can selectively allow access to the session. The architecture facilitates lock and lobby features in multiple identical, leaderless, conference servers which together form a distributed conferencing system. The lock and lobby features can employ media session protocols such as session initiation protocol (SIP) and centralized conference control protocol (C3P).

Abstract: A method of venting a rotational mold at a predetermined condition by actuating an actuating venting assembly pierces the shell of the molded article and introduces a passageway to relieve pressure during the molding cycle. The actuating venting assembly enables a tactical methodology for venting such molds.

Abstract: A steering rack is provided wherein the various components can be friction welded together. The various components can be of various shapes that can include a tube portion friction welded to another tube portion having gear racks thereon. The tubes may have various shapes and may include slots therein. The components may also be welded together using inertia welding.