Microsoft Technology Licensing, LLC

Gagan Chopra

Patrick James Helland

Mohsen M Al-Ghosein

Ahmad Mahdi El Husseini

Arif Kureshy

Dmitry V Zhiyanov

Tanya L Swartz

Misha H St Lorant

Richard Dievendorff

Jayadev Pillai

Girish Premchandran

Srikanth Avadhanam

Matthew C McCline

Siddharth Banothu

Zhaoji Chen

Anand Sampathkumaran

A user trainable user interface page classification system applies a rule set to information associated with a user interface page to determine whether the user interface page satisfies a domain page condition. If the user interface page does not satisfy the domain page condition, a user trains the system such that the user interface page classification system classifies the user interface page as a domain page. The rule set of the user interface page classification system is updated, and the updated rule set is applied to the information associated with the user interface page. The user interface page classification system then classifies the user interface page as a domain page.

User trainable user interface page classification system

A method of facilitating customization of a software-implemented business process includes storing, within a mobile computing device, a subscription list of entities. The subscription list is defined by subscription metadata. Customized data is received. The customized data corresponds to the entities identified in the subscription list. The received customized metadata is stored on the mobile computing device.

Metadata driven customization of a computer application

A method of facilitating customization of a software-implemented business process includes storing, within a mobile computing device, a subscription list of entities. The subscription list being defined by subscription metadata. Customized data is received. The customized data corresponds to the entities identified in the subscription list. The received customized metadata is stored on the mobile computing device.

Metadata driven customization of a software-implemented business process

In a method of customizing a software-implemented business process on a mobile computing device, customized metadata defining customizations of the business process are provided. Next, the metadata is deployed to the mobile computing device and stored in a data store of the mobile computing device. The customizations defined by the metadata are then applied to the software-implemented business process.

The present system aggregates information from a plurality of different context sources. The present system also makes that aggregated information available to requesting components by abstracting it into a generalized form. Thus, the developer of a context-aware application need only know how to interact with the context service of the present invention, rather than knowing how to interact with each and every one of the context sources.

Context service system

Queued component interface passing provides a way for a queued component to convey results of processing a client program's method invocations made asynchronously via a queue. A queued component recorder for a 'processing' queued component operates to marshal-by-value a method invocation parameter that is reference to another queued component recorder for another 'results' queued component into a data stream of recorded method invocations, which is then submitted as a message to a queue associated with the processing queued component. On receipt of the message from the queue, a queued component player for the processing queued component unmarshals the reference to the other queued component recorder and passes this reference to the processing queued component. The processing queued component uses the passed reference to invoke methods of the results queued component through its message queue, which conveys the processing queued component's results.

Queued component interface passing for results outflow from queued method invocations

In a method of managing a synch operation during which business solutions entities are loaded into a mobile data store of a mobile computing device from a central data storage system, subscriptions are defined that identify entities to be loaded into the mobile data store during a synch operation. Next, a remaining data storage capacity of the mobile data store and a subscriptions data quantity corresponding to an amount of data space required to store the entities identified by the subscriptions are estimated. Finally, the subscriptions data quantity is compared to the remaining data storage capacity.

Business application entity subscriptions synch operation management

An object runtime architecture allows method invocations to be made on either a synchronous, real-time basis or a queued basis using the normal call semantics of an object model. The object runtime architecture provides a proxy of an object with a method invocation recorder for receiving method calls of a client on the object, and marshaling the method calls into a message for sending to a queue associated with the object. The object runtime architecture further provides a listener for dispatching the message from the queue to a player which uses a stub to unmarshal the message in order to issue the method calls to the object. The object runtime architecture thus decouples the client and objects lifetimes and availability, without requiring explicit programming of the client and object to perform message queuing. Accordingly, with no modification of the object's interface structure or code, the same object can be used in either a real-time or queued environment. This allows the decision between real-time or queued method invocations to be made much later than at development of the object, such as at run-time creation of the object.

Queued method invocations on distributed component applications

In a computing environment containing a plurality of state machines that communicate by passing messages on connections, a construct called a clique controls access into a set of the state machines by worker threads that deliver the messages arriving on the connections. A clique is a collection of connections into the set of the state machines that have a common relationship for which concurrency isolation is required. Each clique has a message queue and a guard for marking the clique as busy or not busy, The guard prevents more than one thread at a time from delivering messages that arrive on connections in the clique to the set of state machines, thus ensuring concurrency isolation of the set of state machines. Messages that arrive on a connection in the clique while the clique is marked as busy are queued in the clique's message queue. The queued messages are delivered one at a time by a same worker thread that is currently busy in the clique. This operation can save a thread switch when a state machine generates an outgoing message that results in an immediate incoming message to the state machine, such as a buffer full message, and thus makes efficient use of the worker threads.

Growing community of inventors

Redmond, WA, United States of America

Gagan Chopra