Microsoft Technology Licensing, LLC

Yasser Elsayed Shaaban

Mariyan Dimitrov Fransazov

Abolade Gbadegesin

Aaron Lahman

Vishal Vikram Ghotge

Megan Galbraith Donahue

Peter J Torr

Darin Miller

Timothy Daniel Noonan

Jorge I Raastroem

Adrian Dragomir

Rachel Jiang

Chittur Padmanabhan Subbaraman

Marc David McClure

Alexander Jon Dobin

Jianping Yin

Pavan Rajamohan Hullumane

Gregory Arthur De Souza

Adina Magdalena Trufinescu

Sameer Tejani

Prabhat Kumar Pandey

Andrew Michael Pennell

Mei-Chin Tsai

Subramanian Ramaswamy

Casimir Lakshan Fernando

Ashish Babbar

Akhil Gupta

Abhinav Jha

William Hong Vong

Olivier Colle

Abhishek Agarwal

Akhilesh Kaza

Jason William Fuller

David Andrew Whitechapel

Ankit Saraf

David Nissimoff

Anjli Chaudhry

Laura Onu

Arnaud Christian Flutre

Mark David Overholt

Aleksey S Kabanov

Weijia Mao

Siu Yu Cherie Quek

Conrad Chang

Justin Horst

Vijayendra G R Vasu

Ahmed Mohamed Abbas Helmy Mohamed Kotb

Aaron R Lahman

Marc David Mcclure

Peter John Torr

Versions of an application are managed by receiving a request for a version of an application, retrieving, responsive to the received request, a version of a master application component based at least in part on version data that associates a version of the master application component with the version of the application, retrieving a relationship operable to relate the version of the master application component with a corresponding version of a first component on which the master application component depends for a function of the application, retrieving the corresponding version of the first component, responsive to the retrieving of the relationship, assembling the version of the application based at least in part on the retrieved version of the master component, the retrieved relationship, and the retrieved first component, and providing for an execution of the assembled version of the application.

Application module version management

Systems and methods are provided and include a processor, memory, and an application that is stored in the memory and includes instructions. The instructions are configured to initiate a stateful session for the application by sending a session initiation request addressed to a global endpoint and receive a response to the session initiation request from a first server of a first server cluster, the response including a cluster identification associated with the first server cluster. The instructions are further configured to send a session request addressed to the global endpoint, the session request including the cluster identification associated with the first server cluster. The instructions are further configured to receive an error message in response to the session request from a second server of a second server cluster to resend the session request addressed to the first server cluster in response to receiving the error message.

Systems and methods for achieving session stickiness for stateful cloud services with non-sticky load balancers

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

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Background transfer service for applications on mobile devices

Disclosed herein are representative embodiments of tools and techniques for installing, executing, and/or updating managed applications through generation of native code from code in an intermediate language. According to one exemplary technique, a computing device receives machine dependent intermediate language code (MDIL code) generated by an online provider for an application. Additionally, the computing device installs the application on the computing device by generating a native image for the application, which includes binding a portion of the MDIL code with one or more libraries on the computing device. Also, the native image is stored on the computing device for use in loading the application for execution.

Generating native code from intermediate language code for an application

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

Techniques are described for rendering a gallery control to a graphical user interface (GUI), the gallery control including first and second template replicas. For each template replica, a GUI-rendering component is instructed to render the template replica, a read application programming interface (API) call is placed to the GUI-rendering component, a target size of the template replica is determined based on the results of the read API call, and a write API call is scheduled to instruct the GUI-rendering component to update the dimension of the template replica to the target size. In response to determining that the target size of the dimension of either template replica is different than a default size, a write API call is placed to the GUI-rendering component to update an offset associated with each template replica and the scheduled write API calls are placed to the GUI-rendering component.

Gallery control with dynamically determined control template replica sizes

Issuance of job tokens performed by an authorization computing entity so that authoring authorizations can be shared with other authors. Each of the job tokens represents an authorization to engage in a particular manner in an authoring session in which a declarative document is being authored. That engagement includes sharing one or more authorizations with other possible author. The declarative document is a computer program in the form of a list of declarative statements made in a declarative programming language. The management occurs by evaluating incoming requests to engage in various ways in an authoring session.

Share token issuance for declarative document authoring

An integrated application environment includes a host web application executed in a browser, and a target application embedded in a container of the host web application. Interoperability layers facilitate messaging between the host web application and a host entity object of the target application in the container according to multiple communication protocols.

Interoperability between a host application and an embedded target application

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

Growing community of inventors

Seattle, WA, United States of America

Yasser Elsayed Shaaban