Microsoft Technology Licensing, LLC

Gopal Krishna R Kakivaya

Satish Ramchandra Thatte

Andrew Layman

Mihail Gavril Tarta

Anurag Gupta

Jan Stephen Gray

Robert George Atkinson

Richard L Hasha

Henrik Frystyk Nielsen

Craig Henry Wittenberg

Richard Douglas Hill

Jeffrey Bruce Parham

James M Lyon

Rebecca Ann Norlander

Andrew D Milligan

Eric Wendell Johnson

Charles R Reeves

Mert Coskun

Angela Mills

Sumukh Shivaprakash

Scott G Robinson

Lawrence A Buerk

Erik B Christensen

Christopher Wellington Brumme

Michael Joseph Toutonghi

Henrik F Neilsen

A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement 'unlocks' any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Transactional replicator

Embodiments are directed to managing multiple different types of applications using service groups. In one scenario, a computer system receives an indication of one or more application dependencies and characteristics that are to be implemented when an application is provisioned on a distributed host computer system. The computer system creates an application manifest that declaratively defines application dependencies and characteristics for various different service groups. Each service group includes applications that match the declaratively defined application dependencies and characteristics. The computer system also sends the manifest to the distributed host computer system which loads those applications that fit the manifest criteria onto available nodes of the distributed host computer system according to the service groups specified in the manifest.

Distributed application optimization using service groups

A system and methods for service discovery and publication are disclosed. Application programs write requests for service discovery, publication, and subscription to a service discovery application programming interface. The service discovery application programming interface invokes one or more lower-level protocols to satisfy the discovery, publication and/or subscription request. Service information retrieved from lower-layer protocols is formatted into a consistent data model and returned to the client application. In addition, service information may be stored in a persistent data store managed by a discovery persistence service communicatively connected to the service discovery API.

Service discovery and publication

Using a message exchanger ('message exchanger'), data messages are exchanged between entities in a decentralized, distributed, potentially heterogeneous, network environment. The message exchanger employs XML (extensible Markup Language). To accomplish this, the entities on both ends of the message exchange understand, identify, and parse the message format. The message exchanger defines such a mechanism. Data messages are broken down into two portions&#x2014;one portion (the body) is intended from an ultimate destination and the other portion (the header) is intended for intermediate destination and/or the ultimate destination. The body may be defined so that it must be understood by the ultimate destination. The header may be defined so that it must be understood or changed. Regardless, the data in the body is delivered intact to the ultimate destination. The message exchanger defines a message envelope exchange format in XML over a transport protocol, such as HTTP (HyperText Transport Protocol). This format allows for the execution of RPC (Remote Procedure Call) over XML, but it can be used for any message exchange over a network.

Method for exchanging messages between entities on a network comprising an actor attribute and a mandatory attribute in the header data structure

Communication among agile objects and context-bound objects within object-oriented programming environments, including communication across contextual boundaries, is disclosed. In one embodiment, a reference to a second object within a second context is wrapped in a proxy wrapper. A first object within a first context calls the second object via the wrapped reference. No direct reference is held by the first object to the second object. Other embodiments relate to agile objects. Agile objects called by context-bound objects execute in the contexts of their callers. The context of a calling context-bound object becomes the context of an agile object for calling of the agile object by the calling context-bound object. Direct reference to the agile object by the context-bound object is thus permitted.

Communication among agile and context-bound objects

Herein is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.

Object persister

Here is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialed object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.

Described is a system and mechanism by which a client computer may issue a conventional request for a resource on the Web. A response to that request is annotated with information indicating that metadata is available for the resource. Specifically, a special tag or instruction may be included in the response document that indicates the existence and location of a discovery document containing metadata about the resource. The client computer may then retrieve the metadata from the location identified in the response.

System and method for discovering information about web resources

The object persister serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.

Method and system for exchanging messages between entities on a network comprising an actor attribute and a mandatory attribute in the header data structure

An object system provides composable object execution environment extensions with an object model that defines a framework with contexts, policies, policy makers and activators that act as object creation-time, reference creation-time and call-time event sinks to provide processing of effects specific to the environment extensions. At object creation time, an object instantiation service of the object system delegates to the activators to establish a context in which the object is created. The context contains context properties that represent particular of the composable environment extensions in which the object is to execute. The context properties also can act as policy makers that contribute policies to an optimized policy set for references that cross context boundaries. The policies in such optimized sets are issued policy events on calls across the context boundary to process effects of switching between the environment extensions of the two contexts.

Growing community of inventors

Sammamish, WA, United States of America

Gopal Krishna R Kakivaya