Microsoft Technology Licensing, LLC

John R Burkhardt

Jason Evan Schleifer

Ransom Lloyd Richardson

Steven E Lees

Richard Zack Speyer

Raymond Edward Ozzie

Matthew S Augustine

Brian M Lambert

Jack E Ozzie

Paresh S Suthar

Weidong Wang

Reed P Sturtevant

Robert F Goodman

Michael R Gretzinger

Rachel R Schiff

Barnaby M Claydon

Katherine W Rae

Jason E Schleifer

Methods, systems, and computer-readable media are provided to allow multiple server resources to share a single connection to a client device. The single connection may be maintained between a notification queue on the server side and the client device. Multiple server resources share the notification queue. When a resource changes or a service wants to communicate information to a client, corresponding messages are sent to the notification queue over a connection within the data center. Once in the notification queue, the updates are communicated to the client device.

Subscribing to multiple resources through a common connection

Methods, systems, and computer storage media are provided for communicating with client devices by way of a proxy device. An indication is received that multiple client devices are attempting to communicate with a shared service over a wide area network, such as the Internet. A server provides a first client device with a list of other client devices that are currently in communications with the shared service. Once a proxy device has been selected, the server receives an identification of that proxy device from the first client device so that the server knows that future communications from the first client device will be received through the proxy device. Data is then communicated to and from the shared service by way of the proxy device.

Selection of proxy device for connection pooling

Methods, system, and computer storage media are provided for moderating actions performed on shared data objects. Rule enforcement logic is received for an application that is associated with one or more data objects shared between various clients. The rule enforcement logic is stored at a data server that also stores data associated with data objects. A moderator, also stored on the data server, is used to enforce the rule enforcement logic corresponding to the application when a client attempts to perform an action to a data object associated with the application.

Moderation of shared data objects

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.

Shared data collections

Methods, systems, and computer-readable media for manipulating in-memory data entities are provided. Embodiments of the present invention use a Representational State Transfer ('REST') web service to manipulate the in-memory data entities. In one embodiment, a 'snap shot' is taken of the in-memory data entities at a point in time to create representations of the entities. A hierarchy of the representations is built. The hierarchy is used to make the entities addressable via a URI. Embodiments of the invention may then map the entity representations in the hierarchy to the entities. An embodiment of the invention uses handlers to process a REST style request addressed to an entity representation. The handler reads the command and determines whether the command is authorized for performance on the entity and performs that command, if appropriate.

Providing access to shared state data

Methods, system, and computer storage media are provided for enabling cross-language object sharing by providing shareable typename information agreed upon by clients that wish to share object with each other. A first client creates an object by communicating a create request, which includes typename information associated with the object. The object is created and the typename information, along with data and properties associated with the object, is stored. A second client requests to open that object. The data, properties, and typename information stored in associated with the object is communicated to the second client so that the second client is able to create a correct instance of the object.

Cross language object sharing

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.

Sharing and synchronization of objects

Email users may feel overwhelmed with the abundance of emails they receive. Many current email management techniques require at least some manual intervention that may be time consuming and/or otherwise frustrating to a user. As provided herein, emails may be characterized based upon content of the email and domain classification data (e.g., a company name, business category, or a website name associated with the domain name of the sender). One or more viewing panels may be populated with the characterized emails. A viewing panel may present emails corresponding to a particular characterization (e.g., a shopping viewing panel may display emails characterized as shopping). To enhance characterization, rules used to characterize emails may learn from a user's actions. For example, a user may move an email from a shopping viewing panel to a travel viewing panel, thus altering the characterization of the email from shopping to travel.

Email characterization

An API development framework uses a Simple Object Access Protocol (SOAP) protocol to provide access to a collaborative client from a remote user that does not have access to the collaborative software. A WSAP server acts as a bridge between the native collaborative environment and any non-native environment or application that can process SOAP commands and allows the two entities to communicate regardless of firewalls and other security software. The non-native environment can be either local (on the same machine as the collaborative client program) or physically remote (on a different machine). In addition to the server, the illustrative framework includes client side support that is comprised of a SOAP proxy component and remote interfaces to collaborative system objects and platform tools.

Growing community of inventors

Arlington, MA, United States of America

John R Burkhardt