Microsoft Technology Licensing, LLC

Mariyan Dimitrov Fransazov

Yasser Elsayed Shaaban

Aaron Lahman

Ashwin S Needamangala

Romit Chattopadhyay

Alexander Jon Dobin

Herman Widjaja

Justin A Slone

Olivier Colle

Hristo H Ivanov

David Nissimoff

Marius Popa

Arnaud Christian Flutre

Andrew Michael Pennell

Dimitar Popov

Mark David Overholt

Daniel Stelian Mihai

Ying Deng

John R Ashmun

Kantcho I Bogdev

William Hong Vong

Peter Zabback

Anjli Chaudhry

Laura Onu

Feng Yuan

Radu Bogdan Gruian

Aleksey S Kabanov

Muralidhar Sathsahayaraman

Irina Koulinitch

Bao Quoc Nguyen

Weijia Mao

Donny Amalo

Andy M K Cheng

Elliot W Kirk

Patrick T O'Brien

Hemanth Kumar

Anish Mohan

Ling Wo

Michael Hideaki Yamamoto

Ahmed Mohamed Abbas Helmy Mohamed Kotb

Aaron R Lahman

Peter Alfred Zabback

According to examples, a host device may be instructed to pre-spawn a number of first host processes and a number of second host processes, in which the number of first host processes and the number of second host processes are defined in a first scaling constraint and are each greater than or equal to one. The host device may pre-spawn the second host processes in one or more computing nodes through identification of a host process of the first host processes that is unbound from a client session, termination of the identified host process, and pre-spawning of a second host process that provides a second version of the service based on the termination. The host device may also decrease the number of first host processes and increase the number of second host processes in the one or more computing nodes as defined in a second scaling constraint.

Upgrade a version of a service

According to examples, a method for upgrading a version of a service across a plurality of computing nodes may include instructing a host device to pre-spawn a number of first host processes configured to provide a first version of the service in the computing nodes and to pre-spawn a number of second host processes configured to provide a second version of the service according to a first scaling constraint in the computing nodes. The method may also include, in response to receiving an indication that each of the second host processes is operating properly in the computing nodes, instructing the host device to decrease the number of first host processes and to increase the number of second host processes in the computing nodes as defined in a second scaling constraint.

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

An architectural software model in which browser-executable code and non-browser executable code of an application are distributed. The browser-executable code (such as markup language and script) is executed by a browser on perhaps a client machine, whilst the non-browser executable code (such as C# code as an example) is executed on a server or by a service. Such code typically is included within a single desktop application with an interoperability component operating between. The browser-executable code is able to communicate with the non-browser executable code using a request-response protocol. In order to facilitate communication with the non-browser-executable code, the non-browser executable code is provided in an environment that includes a request translator and a response translator. The environment includes an interface which honors the request/response protocol followed by the browser-executable code.

Distributed application based off of stateful desktop 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

According to examples, a method for upgrading a version of a service may include instructing a host device to pre-spawn a number of first host processes configured to provide a first version of the service in a computing node and to pre-spawn a number of second host processes configured to provide a second version of the service according to a first scaling constraint in the computing node. The method may also include, in response to receiving an indication that each of the second host processes is operating properly, instructing the host device to decrease the number of first host processes and to increase the number of second host processes as defined in a second scaling constraint.

In some examples, application startup control may include determining a relationship between a first page and a second page of an application, and generating a first code file for the first page based upon the determined relationship. Application startup control may further include generating a second code file for the second page. The first code file may include code to load the second code file in response to the first code file being loaded and executed.

Application startup control

Aspects of the present disclosure relate to establishing a secure session between a client device and a stateful backend server or host. The system described herein uses an identity token and an authorization token to generate a globally unique identifier that is associated with the client device. The globally unique identifier is then used to create a one-to-one mapping between the client device and the backend server.

Establishing secure sessions for stateful cloud services

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 and receive an initial server response including at least one configuration parameter to be used during the stateful session. The instructions are further configured to determine whether the at least one configuration parameter is not acceptable and send an initial client response to the server in response to a determination that the at least one configuration parameter is not acceptable, the initial client response including a proposed adjustment to the at least one configuration parameter.

Systems and methods for negotiation of structured configuration parameters for stateful server/client systems

According to examples, an apparatus may include a processor and a memory on which is stored machine readable instructions that are to cause the processor to receive, from a first node, a client request and a response corresponding to the processed client request, in which the first node is configured to generate the response by processing the client request on a service and processed client request is configured to change a state of the service. The instructions are also to cause the processor to receive, from the first node, a response corresponding to the received request, generate an entry including the received request and response, commit the generated entry into a journal, and send an acknowledgement of the received request and response to the first node after the generated entry is committed into the journal.

Service state preservation across nodes

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

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.

Growing community of inventors

Kirkland, WA, United States of America

Mariyan Dimitrov Fransazov