Abstract: A realtime kernel supports realtime communications between communicants operating on respective network nodes. The realtime kernel handles the complex tasks of connecting to communicants, virtual areas, and other network resources, switching those connections in response to user inputs, and mixing realtime data streams. The realtime kernel enables developers to focus on developing high-level communications functionality instead of low-level plumbing code. The realtime kernel imposes relatively low computational resource requirements so that realtime communications performance can be achieved using a wide range of computing devices and network connections that currently are available.

Abstract: In association with a virtual area, a first network connection is established with a first network node present in the virtual area and a second network connection is established with a second network node present in the virtual area. Based on stream routing instructions, a stream router is created between the first network node and the second network node. The stream router includes a directed graph of processing elements operable to receive network data, process the received network data, and output the processed network data. On the first network connection, an input data stream derived from output data generated by the first network node is received in association with the virtual area. The input data stream is processed through the stream router to produce an output data stream. On the second network connection, the output data stream is sent to the second network node.

Abstract: In one embodiment of the present invention, a collaboration engine is configured to display shared digital assets consistently across displays. The collaboration engine receives container metadata generated based on a first location and first size of a digital asset within a first scaled workspace displayed on a first display. In response, the collaboration engine computes a second location and second size of the digital asset based on the container metadata and the size of a second scaled workspace. Finally, the collaboration engine configures the second device to display the digital asset within the second scaled workspace based on the second location and the second size. Notably, the container metadata correlates to the appearance of the digital asset on the first display, and the appearance of the digital asset on the second display correlates to the container metadata. Consequently, the appearance of the digital asset is consistent across the displays.

Abstract: In one embodiment of the present invention, a collaboration engine is configured to display shared digital assets consistently across displays. The collaboration engine receives container metadata generated based on a first location and first size of a digital asset within a first scaled workspace displayed on a first display. In response, the collaboration engine computes a second location and second size of the digital asset based on the container metadata and the size of a second scaled workspace. Finally, the collaboration engine configures the second device to display the digital asset within the second scaled workspace based on the second location and the second size. Notably, the container metadata correlates to the appearance of the digital asset on the first display, and the appearance of the digital asset on the second display correlates to the container metadata. Consequently, the appearance of the digital asset is consistent across the displays.

Abstract: Techniques are described to support shared applications, including a shared application that permits retrieval, presentation and traversal of information resources. The innovative techniques enable multiple participants at different locations to both see and interact with assets such as a web-based content. The innovative techniques centralize the functionality of an application that is to be shared. A shared application is executed, during a collaboration, at a centralized location in a manner that does not require any local resources to create an application instance.

Abstract: Techniques are described to support shared applications, including a shared application that permits retrieval, presentation and traversal of information resources. The innovative techniques enable multiple participants at different locations to both see and interact with assets such as a web-based content. The innovative techniques centralize the functionality of an application that is to be shared. A shared application is executed, during a collaboration, at a centralized location in a manner that does not require any local resources to create an application instance.

Abstract: In one embodiment of the present invention, a collaboration engine is configured to display shared digital assets consistently across displays. The collaboration engine receives container metadata generated based on a first location and first size of a digital asset within a first scaled workspace displayed on a first display. In response, the collaboration engine computes a second location and second size of the digital asset based on the container metadata and the size of a second scaled workspace. Finally, the collaboration engine configures the second device to display the digital asset within the second scaled workspace based on the second location and the second size. Notably, the container metadata correlates to the appearance of the digital asset on the first display, and the appearance of the digital asset on the second display correlates to the container metadata. Consequently, the appearance of the digital asset is consistent across the displays.

Abstract: A realtime kernel supports realtime communications between communicants operating on respective network nodes. The realtime kernel handles the complex tasks of connecting to communicants, virtual areas, and other network resources, switching those connections in response to user inputs, and mixing realtime data streams. The realtime kernel enables developers to focus on developing high-level communications functionality instead of low-level plumbing code. The realtime kernel imposes relatively low computational resource requirements so that realtime communications performance can be achieved using a wide range of computing devices and network connections that currently are available.