Microsoft Technology Licensing, LLC

Aaron Lahman

Mariyan Dimitrov Fransazov

Yasser Elsayed Shaaban

Alexander Jon Dobin

Kenneth W Sykes

Lawrence William Osterman

Feng Yuan

Aleksey S Kabanov

Hart Wilson

Benjamin Kuhn

Bao Quoc Nguyen

Joaquin Guanter Gonzalbez

Anish Mohan

A system is provided for an application executed by a client to invoke a remote object method of a remote object of a remote object class that is hosted by a server. The application instantiates a proxy of a proxy class that includes a proxy member function with the same signature as the remote object member function. The application associates an object identifier with the proxy. The application invokes the proxy member function of the proxy. Under control of the invoked proxy member function, the application sends to the server an invocation request message that includes the object identifier that is associated with the proxy and an identifier of the remote object member function. The application relies on functionality provided by the browser without the need for the browser to access add-on functionality when executing the application.

Object-oriented remote procedure calls for browser applications

A system is provided for synchronizing a property value between a proxy of an application of a client and a corresponding remote object of a server. The application instantiates a proxy of a proxy class corresponding to a remote object of a remote object class where the proxy class specifies a property with a proxy getter. The application sends to the server an invocation request message to invoke a remote object member function of a remote object and receives an invocation response message. When the invocation response message includes a property update, the application extracts from the invocation response message the value of the property from the property update and stores the extracted value in the proxy. When the proxy getter for the property is invoked, the value of the property can be retrieved from the proxy without having to send an invocation request message to the server.

Synchronization of property values between a client and a server

A system is provided for an application executing at a client to send invocation requests to remote objects of a server. Each invocation request is generated when the application invokes a proxy of a proxy class of the application corresponding to a remote object of a remote object class. For each invocation request, when the invocation request is deferrable, the system stores the invocation request. When the invocation request is not deferrable, the system sends to the server an invocation request message that includes each stored invocation request not previously sent and the current invocation request. The system receives invocation response messages from the server. For each invocation response of a received invocation response message, the system provides to the application an indication that the invocation response has been received.

Deferring invocation requests for remote objects

Techniques are described herein for the development of an application that includes both standalone and web-based versions. Both versions share substantial portions of code, thereby minimizing the disparity between the versions in terms of function and user experience. The foregoing also enables the web-based application to be operable in an offline environment. This may be achieved by separating both the standalone and the offline web-based versions into a client portion and a server portion, but having both portions executing on the client. Instead of facilitating communication between these portions via a network communication channel, communication is performed via an emulated network communication channel, which translates network requests and responses provided by these portions into a format suitable for transmission over the emulated network communication channel. By doing so, these portions can be reused and function identically in standalone versions, online web-based versions, and offline web-based versions of the application.

Code base sharing between standalone and web-based versions of an application via an emulated network communication channel

Interface identifier parameterization techniques are described. In one or more implementations, a textual description is obtained of a parametric type represented in a binary standard of a programming model and an interface identifier is generated based at least in part on the obtained textual description of the parametric type.

Parameterized interface identifier techniques

Block based image processing techniques are described in which one or more processing filters are applied to an image block by block. One or more filters are identified to process an image. Attributes are obtained that describe the one or more filters. Image data is loaded into multiple input blocks based upon the obtained attributes. The one or more filters are applied to the image block by block. The results of the processing may be stored as multiple processed blocks corresponding to the multiple input blocks. Then, the processed blocks are stitched together to form a processed image.

Block based image processing

Various embodiments can provide a tool aimed at identifying document conditions that can lead to processing bottlenecks when an associated document is consumed, such as by being rendered or printed, by a particular device. In at least some embodiments, the tool can identify or diagnose such conditions and report those conditions to an appropriate entity, such as a device that produced the associated document and/or an individual who caused the document to be produced. The reporting functionality may include, in at least some embodiments, remedial recommendations aimed at mitigating the diagnosed conditions.

Growing community of inventors

Redmond, WA, United States of America

Aaron Lahman