Browse Prior Art Database

A Method and System for Utilizing an Asynchronous Remote Procedure Call State Machine Design

IP.com Disclosure Number: IPCOM000237666D
Publication Date: 2014-Jul-02
Document File: 3 page(s) / 137K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for utilizing an asynchronous remote procedure call state machine design.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

A Method and System for Utilizing an Asynchronous Remote Procedure Call State Machine Design

Disclosed is a method and system for utilizing an asynchronous Remote Procedure Call (RPC) state machine design.

The asynchronous RPC state machine enables authorized users to send long running requests to a server, allowing a client to control processing of the request. A long

running process runs on a server for an extended length of time. The client can specify the frequency of status message updates as a user request is being processed. The asynchronous mechanism allows a request to be made without consuming network resources for the entire duration of the long running server process, while providing

status updates to the client. The state machine design overcomes the issue of network

timeouts that could arise from these requests. A client can also send a halt request to

the server process to abort.

A user request from a client triggers a long running process on the server. The states of a running process are set by the client or the server. The current state reflects the progress of the RPC. Client states include initiating the RPC, acknowledging completion or exception processed by the server RPC. Server states are states executing from the beginning of processing to the completion along with any exceptions.

The following describes the design features of the asynchronous RPC State Machine.

A client server connection opens for the request and status checks from the client, leaving network connections available for other client requests. Server requests taking longer than the connection timeout still provide informational messages back to the client application as the server process progresses.

The client initiates an incoming asynchronous RPC to begin a long running command.

An RPC record is written to an asynchronous RPC record database table. Each task request includes a unique sequence number which is used as a task identity (ID). Thereafter, a long running thread is started to process the command.

The asynchronous RPC state machine design utilizes database tables to manage tasks started from the client applications through the RPC. Each RPC task is recorded in the asynchronous record table. This entry contains asynchronous status, times...