Abstract: One or more techniques and/or systems are disclosed herein for relaying a request to a process running on a computing device from a web client and receiving a response from the process. A bridge message client disposed in a web application, running in a browser on a computer, opens a local connection to a process running outside the browser. The bridge message client comprises a communication channel ID that identifies a communication channel to host the local connection to a bridge server, and a bridge message client ID facilitates communications from the bridge server to the web application. The bridge server is disposed outside of the browser environment, and can receive a request from the bridge message client and forward it to the process, and/or can receive a response to the request from the process and forward it to the bridge message client over the local connection.

Abstract: A technique and mechanism to effect cross-pollination synchronization of PIM (personal information manager) data to multiple sources. Additionally, a novel feature of the subject invention is the ability to effect cross-pollination synchronization with any number of devices and sources in a network. The invention provides for a user to employ a mobile device or set of devices as a central repository for PIM data (e.g., calendar, contacts and tasks) synchronized from multiple sources (e.g., multiple PC's (personal computers), an exchange server). The invention provides for synchronization of PIM data from multiple types of server sources to multiple devices regardless of the synchronization protocol versions and different schemas.

Abstract: One or more techniques and/or systems are disclosed herein for assigning familiar pseudonames to anonymous user members in a shared online environment. Creation of a name pool is provided for using a programmed processor disposed in a computing device. The name pool includes familiar names that may be contextually relevant to a group of user members in the shared online environment. A name from the name pool is provided for assignment to an anonymous user member in the shared online environment, where assignment of the name is, at least in part, based on characteristics of the anonymous user member relative to the shared online environment.

Abstract: A data sharing mechanism may allow programs to share access to data collections. The mechanisms that implement the sharing may allow programs written in any language to read and write a shared collection. The mechanisms may make the shared nature of the collection relatively transparent to the program and to the programmer, by allowing a program to operate on the data more or less as if it were purely local data. The sharing of collections may be managed by a shared object runtime on each machine on which a collection is used, and by a shared object server. The shared object server maintains the true state of the collection, and deterministically resolves collections when programs operate on the same collection without knowledge of each other's operations. The mechanisms by which collections are shared may be implemented so as to be agnostic as to the kind of data in the collection.

Abstract: Users of various devices may participate in communication sessions, but only if the interfaces and components of such devices feature a minimum set of capabilities involved in the communication session type; e.g., in order to participate in a teleconference, the device of every user has to be capable of sending and receiving audio. Instead, a communication session server may automatically convert session items received from each user into interface-specific representations for each other user, based on the capabilities of the interface and device of the other user. For example, speech recognition may transform speech to text output; speech synthesis may transform text input to speech; and video recognition may identify individuals and gestures in a video stream and represent this information as text. The server may therefore host a “mixed” communication session, where each user may fully participate irrespective of the capabilities of the chosen device and interface.

Abstract: Sharing of objects may be implemented in a way that allows programs to use shared objects in much the same way that they would use local objects. In one example, a program creates an object and sets properties through normal instructions that would be used to create a local object. The program then registers the object with a shared object model, which may be maintained by a shared object server. For each machine on which the object may be used, a shared object runtime monitors for changes to the objects, and notifies the server of these changes. The server updates the object, and notifies other machines of changes to the state of the object. The shared object runtimes on those machines receive notification of the changes, and update the local copies.

Abstract: A technique and mechanism to effect cross-pollination synchronization of PIM (personal information manager) data to multiple sources. Additionally, a novel feature of the subject invention is the ability to effect cross-pollination synchronization with any number of devices and sources in a network. The invention provides for a user to employ a mobile device or set of devices as a central repository for PIM data (e.g., calendar, contacts and tasks) synchronized from multiple sources (e.g., multiple PC's (personal computers), an exchange server). The invention provides for synchronization of PIM data from multiple types of server sources to multiple devices regardless of the synchronization protocol versions and different schemas.

Abstract: A data sharing mechanism may allow programs to share access to data collections. The mechanisms that implement the sharing may allow programs written in any language to read and write a shared collection. The mechanisms may make the shared nature of the collection relatively transparent to the program and to the programmer, by allowing a program to operate on the data more or less as if it were purely local data. The sharing of collections may be managed by a shared object runtime on each machine on which a collection is used, and by a shared object server. The shared object server maintains the true state of the collection, and deterministically resolves collections when programs operate on the same collection without knowledge of each other's operations. The mechanisms by which collections are shared may be implemented so as to be agnostic as to the kind of data in the collection.

Abstract: Sharing of objects may be implemented in a way that allows programs to use shared objects in much the same way that they would use local objects. In one example, a program creates an object and sets properties through normal instructions that would be used to create a local object. The program then registers the object with a shared object model, which may be maintained by a shared object server. For each machine on which the object may be used, a shared object runtime monitors for changes to the objects, and notifies the server of these changes. The server updates the object, and notifies other machines of changes to the state of the object. The shared object runtimes on those machines receive notification of the changes, and update the local copies.

Abstract: Users of various devices may participate in communication sessions, but only if the interfaces and components of such devices feature a minimum set of capabilities involved in the communication session type; e.g., in order to participate in a teleconference, the device of every user has to be capable of sending and receiving audio. Instead, a communication session server may automatically convert session items received from each user into interface-specific representations for each other user, based on the capabilities of the interface and device of the other user. For example, speech recognition may transform speech to text output; speech synthesis may transform text input to speech; and video recognition may identify individuals and gestures in a video stream and represent this information as text. The server may therefore host a “mixed” communication session, where each user may fully participate irrespective of the capabilities of the chosen device and interface.

Abstract: One or more techniques and/or systems are disclosed for presenting members of a shared online space to a user of the shared online space. A relationship value is determined between the user and a member of the shared online space by: determining an interaction value for the user and member relationship based on the user's and member's co-presence in the shared online space; determining a social network value for the user and member relationship based on a number of social network connections between the user and member; and combining the interaction value and social network value. The relationship value is associated with a specified visual representation of the member used in the shared online space, and two or more visual representations of members are scaled in the user's display in the shared online space in order to fit an available screen space, based on the relationship value.

Abstract: One or more techniques and/or systems are disclosed herein for relaying a request to a process running on a computing device from a web client and receiving a response from the process. A bridge message client disposed in a web application, running in a browser on a computer, opens a local connection to a process running outside the browser. The bridge message client comprises a communication channel ID that identifies a communication channel to host the local connection to a bridge server, and a bridge message client ID facilitates communications from the bridge server to the web application. The bridge server is disposed outside of the browser environment, and can receive a request from the bridge message client and forward it to the process, and/or can receive a response to the request from the process and forward it to the bridge message client over the local connection.

Abstract: A carrying device includes an elongated strap having first and second ends, at least one clamp at least proximally coupled to one of the first and second ends of said elongated strap, and a securement device coupled to a region proximate at least one of the first and second ends of said elongated strap for coupling together the regions proximate the first and second ends of the elongated strap.

Abstract: A carrying device includes an elongated strap having first and second ends, at least one clamp at least proximally coupled to one of the first and second ends of said elongated strap, and a securement device coupled to a region proximate at least one of the first and second ends of said elongated strap for coupling together the regions proximate the first and second ends of the elongated strap.