US 2019/0196891 A1Published application

Object-oriented remote procedure calls for browser applications

AssigneeMicrosoft Technology Licensing, LLC

InventorsAaron Lahman, Yasser Shaaban, Mariyan Fransazov, Alexander Jon Dobin

Life of this patent

Estimating the term…

Loading patent…

Abstract

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.

Claims20

Dependent claims

A client configured to send invocation requests of an application to remote objects of a server, the client comprising:

a processor that executes computer-executable instructions;
and
a memory that stores computer-executable instructions that, when executed by the processor, control the client to:
receive invocation requests that include deferrable invocation requests and non-deferrable invocation requests, each invocation request received from a proxy of a proxy class of the application corresponding to a remote object of a remote object class;
for each received deferrable invocation request, store the received deferrable invocation request;
for each received non-deferrable invocation request, send to the server an invocation request message that includes the received non-deferrable invocation request and each stored invocation request not previously sent;
receive from the server invocation response messages, each invocation response message received in response to an invocation request message, at least one received invocation response message including multiple invocation responses;
and
for each invocation response of a received invocation response message,
extract any included output parameter, and
provide to the application an indication that the invocation response has been received and any extracted output parameter.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/292,045Filed 4 Mar 2019
Priority: 30 Jan 2017
Published: 27 Jun 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

G06F 9/548
Remote procedure calls [RPC]; Web services: object oriented; Remote method invocation [RMI]
G06F 9/547
Interprogram communication: remote procedure calls [RPC]; Web services
H04L 67/025
Based on web technology, e.g. hypertext transfer protocol [HTTP]: for remote control or remote monitoring of applications
H04L 67/561
Provisioning of proxy services: adding application-functional data or data for application control, e.g. adding metadata

Family

Application15/420,001Continuation · filed 30 Jan 2017
Application16/292,045Continuation
US 10,223,181 B2Related patent
US 11,010,219 B2Related patent
US 2018/0217886 A1Published application
US 2019/0196891 A1This patent

From the US filing history. Foreign family members aren’t listed.